https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108132
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Status|REOPENED |RESOLVED
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to qinzhao from comment #5)
> To me, this is an important bug that GCC should fix. making it as a
> duplication of an Old bug and closing it seems not a good idea.
Well it is an old bug inside GCC. I am not saying it is not an important bug to
fix but nobody has fixed it as setjmp/longjmp is less wildly used these days
and most programmers who use it usually just add volatile to fix issues with
their code and work around bugs in the compiler.
There is a patch in PR 57067 even which you could try to port to a newer
compiler version and fix up.
*** This bug has been marked as a duplicate of bug 57067 ***
