public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/115135] [C++] GCC produces wrong code at certain inlining levels on Aarch64 with -fno-exceptions, related to lambdas and variants
Date: Tue, 21 May 2024 13:29:08 +0000 [thread overview]
Message-ID: <bug-115135-4-4eRoD9yRNA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115135-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115135
Sam James <sjames at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |ipa
--- Comment #5 from Sam James <sjames at gcc dot gnu.org> ---
(In reply to Carlos Alberto Lopez Perez from comment #2)
> -fno-ipa-modref helps! passing this flag makes the compiled program is
> correct :)
-> calling it an IPA issue.
Carlos, if you can find a version which worked before, could you bisect?
next prev parent reply other threads:[~2024-05-21 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 12:52 [Bug target/115135] New: " clopez at igalia dot com
2024-05-17 13:25 ` [Bug middle-end/115135] " pinskia at gcc dot gnu.org
2024-05-17 15:51 ` clopez at igalia dot com
2024-05-20 18:10 ` clopez at igalia dot com
2024-05-20 18:50 ` clopez at igalia dot com
2024-05-21 13:29 ` sjames at gcc dot gnu.org [this message]
2024-05-21 13:31 ` [Bug ipa/115135] " clopez at igalia dot com
2024-05-21 13:36 ` clopez at igalia dot com
2024-05-21 13:38 ` sjames at gcc dot gnu.org
2024-05-21 14:00 ` [Bug ipa/115135] [12/13/14/15 regression] " clopez at igalia dot com
2024-05-29 11:37 ` [Bug ipa/115135] [12/13/14/15 regression] [C++] GCC produces wrong code at certain inlining levels on Aarch64 with -fno-exceptions, related to lambdas and variants since r12-5113-gd70ef65692fced sjames at gcc dot gnu.org
2024-06-23 3:00 ` pinskia 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-115135-4-4eRoD9yRNA@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).