public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111764] [11/12/13 Regression] Wrong code at -O3 on x86_64-linux-gnu
Date: Thu, 12 Oct 2023 08:22:35 +0000 [thread overview]
Message-ID: <bug-111764-4-pi5Lcp1MlC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111764-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111764
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Known to work| |14.0
Keywords|needs-bisection |
Summary|[11/12/13/14 Regression] |[11/12/13 Regression] Wrong
|Wrong code at -O3 on |code at -O3 on
|x86_64-linux-gnu |x86_64-linux-gnu
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
next prev parent reply other threads:[~2023-10-12 8:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 20:54 [Bug tree-optimization/111764] New: Wrong code at -O3 on x86_64-linux-gnu since r11-5965-g04bff1bbfc1 shaohua.li at inf dot ethz.ch
2023-10-10 20:57 ` [Bug tree-optimization/111764] [11/12/13/14 Regression] Wrong code at -O3 on x86_64-linux-gnu pinskia at gcc dot gnu.org
2023-10-10 21:00 ` pinskia at gcc dot gnu.org
2023-10-11 13:36 ` rguenth at gcc dot gnu.org
2023-10-11 13:47 ` rguenth at gcc dot gnu.org
2023-10-12 6:49 ` rguenth at gcc dot gnu.org
2023-10-12 7:12 ` rguenth at gcc dot gnu.org
2023-10-12 8:22 ` cvs-commit at gcc dot gnu.org
2023-10-12 8:22 ` rguenth at gcc dot gnu.org [this message]
2023-11-10 14:24 ` [Bug tree-optimization/111764] [11/12/13 " cvs-commit at gcc dot gnu.org
2023-11-27 13:09 ` [Bug tree-optimization/111764] [11/12 " cvs-commit at gcc dot gnu.org
2023-12-15 12:18 ` [Bug tree-optimization/111764] [11 " cvs-commit at gcc dot gnu.org
2023-12-15 12:22 ` rguenth 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-111764-4-pi5Lcp1MlC@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).