Closed simonpintarelli closed 6 months ago
Can this patch be upstreamed (to spack) instead?
I'll submit the PR to spack directly and see what happens. I'm not sure how it is handled correctly. I think at some point a new gcc 12.3.1
will be released including this patch.
What will happen when the gcc package is updated upstream? For how long would > you keep this package definition here to replace the one from upstream?
For sure the patch/package should be removed from stackinator once a gcc release is available which includes this patch.
@msimberg I've opened a PR in spack: https://github.com/spack/spack/pull/43093
Let's drop this PR if they merged it.
Closing this PR. The patch for gcc12/13 have been merged in spack@develop.
gcc 12.3.0 had an ICE in aarch64 SVE: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111478
It failed to compile q-e-sirius and py-scipy for example.
Add gcc to local repository together with a patch obtained from https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=9d033155254ac6df5f47ab32896dbf336f991589