https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
Sam James changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
--- Comment #9 from Christophe Lyon ---
I have opened https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118152 about the
sync/atomic failure.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
--- Comment #8 from Vladimir Makarov ---
I reverted the 1st patch variant for PR117248 which resulted in this PR.
I submitted a different patch for PR117248 which does not create new failures
for libgo tests on arm.
Still it would be nice to r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
--- Comment #7 from Sam James ---
Christoph, looking at the reference build (i.e. before Vlad's commit) in
https://inbox.sourceware.org/gcc-regression/1736588063.82421.1733571291005@jenkins.jenkins/T/#u,
I see a bunch of prior failures like:
```
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
--- Comment #6 from Vladimir Makarov ---
I've tried arm GCC before and after the patch. I see failures before the patch
too (e.g. net failed with the same wrong address or nil dereference as crypto)
although, I should acknowledge, less than af
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
--- Comment #5 from Christophe Lyon ---
Note that the test passed before commit r15-5997-g75e7d1600f4785 , which was
bisected by the CI.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117999
Andrew Pinski changed:
What|Removed |Added
Summary|[15 regression] libgo |[15 regression] libgo
