<html>#2818: failing tests with gcc-14
<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>Comment (by Roland Haas):</p>
<p>Yes, I will rename the variable. Yes, <code>_FOO</code> is reserved by compiler / standard library I think. </p>
<p>The thing that has me worried is that with the change in the diff the tests all pass with gcc-14 (well other than ones that are failing for reasons such as schedule issues or hwloc not liking my efficiency cores in my workstation) but without the change many tests in CarpetX fail. All the failing CarpetX tests also pass if I compile with gcc-13 instead of gcc-14. </p>
<p>gcc-14 produces some other warnings (like reporting that index -1 is out of bounds for a <code>double foo[3]</code> vector, which is true) but I have a harder time finding out exactly what line triggers it. </p>
<p>So this seems like I am just perturbing something out of existence. </p>
<p>I’ll propose a the change in a pull request.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2818/failing-tests-with-gcc-14'>https://bitbucket.org/einsteintoolkit/tickets/issues/2818/failing-tests-with-gcc-14</a></p>
</html>