public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111792] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-3414-g0cfc9c953d0221
Date: Tue, 17 Oct 2023 13:59:25 +0000 [thread overview]
Message-ID: <bug-111792-4-AADgP9K6HA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111792-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111792
Patrick Palka <ppalka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
CC| |amacleod at redhat dot com,
| |ppalka at gcc dot gnu.org
Summary|[14 Regression] wrong code |[14 Regression] wrong code
|at -O3 on x86_64-linux-gnu |at -O3 on x86_64-linux-gnu
| |since
| |r14-3414-g0cfc9c953d0221
--- Comment #2 from Patrick Palka <ppalka at gcc dot gnu.org> ---
Started with r14-3414-g0cfc9c953d0221
next prev parent reply other threads:[~2023-10-17 13:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 6:28 [Bug tree-optimization/111792] New: wrong code at -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2023-10-13 6:59 ` [Bug tree-optimization/111792] [14 Regression] " rguenth at gcc dot gnu.org
2023-10-17 13:14 ` rguenth at gcc dot gnu.org
2023-10-17 13:59 ` ppalka at gcc dot gnu.org [this message]
2023-11-05 22:24 ` [Bug tree-optimization/111792] [14 Regression] wrong code at -O3 on x86_64-linux-gnu since r14-3414-g0cfc9c953d0221 pinskia at gcc dot gnu.org
2023-11-10 16:23 ` jakub at gcc dot gnu.org
2023-11-13 9:42 ` rguenth at gcc dot gnu.org
2023-11-13 12:40 ` cvs-commit at gcc dot gnu.org
2023-11-13 12:41 ` 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-111792-4-AADgP9K6HA@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).