public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107523] [13 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu since r13-3628-g6fd485d15c1a2c42
Date: Thu, 10 Nov 2022 15:39:50 +0000 [thread overview]
Message-ID: <bug-107523-4-tBOQXdoxYX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107523-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107523
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[13 Regression] wrong code |[13 Regression] wrong code
|at -O2 and -O3 on |at -O2 and -O3 on
|x86_64-linux-gnu |x86_64-linux-gnu since
| |r13-3628-g6fd485d15c1a2c42
Last reconfirmed| |2022-11-10
CC| |amacleod at redhat dot com,
| |marxin at gcc dot gnu.org
Keywords|needs-bisection |
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r13-3628-g6fd485d15c1a2c42.
next prev parent reply other threads:[~2022-11-10 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 7:25 [Bug tree-optimization/107523] New: wrong code at -O2 and -O3 on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2022-11-04 19:45 ` [Bug tree-optimization/107523] [13 Regression] " pinskia at gcc dot gnu.org
2022-11-10 15:39 ` marxin at gcc dot gnu.org [this message]
2022-11-11 19:48 ` [Bug tree-optimization/107523] [13 Regression] wrong code at -O2 and -O3 on x86_64-linux-gnu since r13-3628-g6fd485d15c1a2c42 cvs-commit at gcc dot gnu.org
2022-11-11 19:54 ` amacleod at redhat dot com
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-107523-4-tBOQXdoxYX@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).