[Bug tree-optimization/114872] [13/14/15 Regression] Miscompilation with -O2 after commit r13-8037
jakub at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Tue May 7 10:45:05 GMT 2024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114872
--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Sergei Trofimovich from comment #18)
> > 2) ideally show a gdb session with the important events, which setjmp was it (I see _setjmp and __sigsetjmp calls in the function), which exact function called from the function ended up aborting/doing longjmp in the signal handler and where is the crash
Strange. If it is the _setjmp call on line 26315 followed by kill SIGABRT from
sig_error(); on the same line, then I don't see any local vars modified in
between, except that int t on line 26315 inside of sig_GAP_Enter macro.
There is then __sigsetjmp on line 26324, but no further kill calls and I think
this isn't in a loop.
More information about the Gcc-bugs
mailing list