<table border="1" cellspacing="0" cellpadding="8">
    <tr>
        <th>Issue</th>
        <td>
            <a href=https://github.com/llvm/llvm-project/issues/95454>95454</a>
        </td>
    </tr>

    <tr>
        <th>Summary</th>
        <td>
            Backport 493422ecb4451b721fe6e66b17292bad7578bc3e to release/18.x
        </td>
    </tr>

    <tr>
      <th>Labels</th>
      <td>
            new issue
      </td>
    </tr>

    <tr>
      <th>Assignees</th>
      <td>
      </td>
    </tr>

    <tr>
      <th>Reporter</th>
      <td>
          johnplatts
      </td>
    </tr>
</table>

<pre>
    /cherry-pick 493422ecb4451b721fe6e66b17292bad7578bc3e

Backporting the fix in commit 493422ecb4451b721fe6e66b17292bad7578bc3e to the release/18.x branch should resolve issues #92615 and #92602.

Are there plans to release an LLVM 18.1.8 release as the backport of commit 493422ecb4451b721fe6e66b17292bad7578bc3e to the release/18.x branch fixes a major bug with LLVM on the s390x target?
</pre>
<img width="1px" height="1px" alt="" src="http://email.email.llvm.org/o/eJysUj1v3CAY_jV4QWeZF2zDwHBR5ClduwN-z-aCjQX4cvn31X1UabdWygIC6fnUY3L204qoSftC2tfK7GWOSZ_jvG7BlJIrG8dPTWBwM6b0edi8e6dCcQGAzgrRMtsDO2GHXWdZDwqsGfu2l9ZxJM0raY6P88W49y2m4teJlhnpyV-pX6mLy-LLPzPSEu_ohAFNRgIDk_WV2mRWN9M8xz2MNGGO4YLU57xjpgS4go611Kzj89FA_ae3Y8Iba0K6BbPmm8hTgJqVvr39_EGZrFktv77z3YZ9hqLx9L1JTv6KmRq6mHNM1O4T_fBlfliJ6x2YuWqutJg0YSF8qEbNR8WVqVCznknetFKpatYNd1J0aBQaaaUdmeidlaqVlpvWCVF5DQ2IpmOcKca4rDkTUjTWghXCOMaJaHAxPtQhXJY6pqm6N6tVK1pRBWMx5PuAAFb8eNROAG57SvqGOdh9ykQ0weeSv1iKLwH172H8V3N_t1btKei5lC0TfiQwEBgmX-bd1i4uBIab4vM6bCme0RUCw2MeBIZHjouGXwEAAP__zLDx2g">