public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/108132] Wrong instruction scheduling around function call with longjmp on aarch64 at O2
Date: Thu, 15 Dec 2022 19:33:52 +0000 [thread overview]
Message-ID: <bug-108132-4-4cAZEEaXXN@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108132-4@http.gcc.gnu.org/bugzilla/>
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 ***
next prev parent reply other threads:[~2022-12-15 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 17:51 [Bug rtl-optimization/108132] New: " qinzhao at gcc dot gnu.org
2022-12-15 17:55 ` [Bug rtl-optimization/108132] " qinzhao at gcc dot gnu.org
2022-12-15 17:56 ` qinzhao at gcc dot gnu.org
2022-12-15 18:02 ` pinskia at gcc dot gnu.org
2022-12-15 18:06 ` pinskia at gcc dot gnu.org
2022-12-15 19:30 ` qinzhao at gcc dot gnu.org
2022-12-15 19:33 ` pinskia at gcc dot gnu.org [this message]
2022-12-15 19:40 ` qing.zhao at oracle dot com
2023-01-13 18:33 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-108132-4-4cAZEEaXXN@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).