public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109344] feraiseexcept produces incorrect code when optimizations are enabled
Date: Thu, 30 Mar 2023 12:23:28 +0000 [thread overview]
Message-ID: <bug-109344-4-6ajd9dwQgc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109344-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109344
--- Comment #5 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to albin from comment #4)
> Thanks for the info. If it was fixed three years ago how come it is still
> seen when using gcc (trunk) on Compiler Explorer? Is Compiler Explorer using
> an obsolete glibc?
It uses Glibc-2.31: https://godbolt.org/z/h348q7fbh
prev parent reply other threads:[~2023-03-30 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 7:49 [Bug c++/109344] New: " albin at yahoo dot com
2023-03-30 10:17 ` [Bug c++/109344] " xry111 at gcc dot gnu.org
2023-03-30 11:09 ` jakub at gcc dot gnu.org
2023-03-30 11:21 ` xry111 at gcc dot gnu.org
2023-03-30 12:18 ` albin at yahoo dot com
2023-03-30 12:23 ` xry111 at gcc dot gnu.org [this message]
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-109344-4-6ajd9dwQgc@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).