<html>#2381: update Vector's AltiVec support
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Summit uses POWER9 processors, whose AltiVec SIMD engine accumulated bugs in Vectors. Pull request <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactusutils/pull-requests/24/vectors-updates-for-altivec-and-knl/diff" rel="nofollow">https://bitbucket.org/cactuscode/cactusutils/pull-requests/24/vectors-updates-for-altivec-and-knl/diff</a> addresses these.</p>
<p>The pull request is from just before the Mayer release and has seen extensive discussion between <span class="ap-mention" data-atlassian-id="557058:56049c54-f8c2-4b6c-9b88-ab697c967495">@Erik Schnetter</span> and myself as well as triggering creating a better test harness for Vectors (see #2380).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2381/update-vectors-altivec-support'>https://bitbucket.org/einsteintoolkit/tickets/issues/2381/update-vectors-altivec-support</a></p>
</html>