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 middle-end/109967] [11/12/13/14 Regression] Wrong code at -O2 on x86_64-linux-gnu
Date: Mon, 25 Sep 2023 15:02:01 +0000 [thread overview]
Message-ID: <bug-109967-4-RuwnxW8qcO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109967-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109967
Xi Ruoyao <xry111 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xry111 at gcc dot gnu.org
--- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to Shaohua Li from comment #7)
> This test case does not reproduce anymore on the current trunk. Maybe one of
> the recent fixes fixed the underlying issue as well.
But we still need to ensure the fix backported into 11/12/13. And there is
still a chance that the issue might be covered up by an unrelated change.
next prev parent reply other threads:[~2023-09-25 15:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 14:15 [Bug c/109967] New: " shaohua.li at inf dot ethz.ch
2023-05-25 18:16 ` [Bug middle-end/109967] " pinskia at gcc dot gnu.org
2023-05-25 18:19 ` [Bug middle-end/109967] [10/11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-05-26 6:01 ` rguenth at gcc dot gnu.org
2023-06-05 11:13 ` davmac at davmac dot org
2023-06-05 15:39 ` amonakov at gcc dot gnu.org
2023-07-07 10:45 ` [Bug middle-end/109967] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-07-28 11:47 ` shaohua.li at inf dot ethz.ch
2023-09-25 12:59 ` shaohua.li at inf dot ethz.ch
2023-09-25 15:02 ` xry111 at gcc dot gnu.org [this message]
2023-09-25 17:27 ` xry111 at gcc dot gnu.org
2024-02-08 18:54 ` jakub 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-109967-4-RuwnxW8qcO@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).