public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clopez at igalia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/115135] [C++] GCC produces wrong code at certain inlining levels on Aarch64 with -fno-exceptions, related to lambdas and variants
Date: Mon, 20 May 2024 18:10:20 +0000	[thread overview]
Message-ID: <bug-115135-4-6zYIfxXiyK@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

--- Comment #3 from Carlos Alberto Lopez Perez <clopez at igalia dot com> ---
Note: I just tested to build GCC from master branch (version 15.0.0 20240520:
commit e14c673ea9ab2eca5de4db91b478f0b5297ef321) and the issue is still
reproducible with it.

  parent reply	other threads:[~2024-05-20 18:10 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 [this message]
2024-05-20 18:50 ` clopez at igalia dot com
2024-05-21 13:29 ` [Bug ipa/115135] " sjames at gcc dot gnu.org
2024-05-21 13:31 ` 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-6zYIfxXiyK@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).