public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/102627] [11/12 Regression] wrong code with "-O1"
Date: Wed, 06 Oct 2021 10:32:35 +0000 [thread overview]
Message-ID: <bug-102627-4-CS8qH41FKt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102627-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102627
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-10-06
Target Milestone|--- |11.3
Component|tree-optimization |rtl-optimization
Priority|P3 |P2
Status|UNCONFIRMED |NEW
CC| |jakub at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
Summary|wrong code with "-O1" |[11/12 Regression] wrong
| |code with "-O1"
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r11-8008-g4bbd51afaa4a3c116fb538d912b35e126be80b41 (at least on
the #c1 testcase at -O1, I don't see any aliasing issue nor any other UB in the
source there so e.g. -fno-strict-aliasing or -fwrapv isn't needed) so possibly
a RA issue.
next prev parent reply other threads:[~2021-10-06 10:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 8:37 [Bug tree-optimization/102627] New: " suochenyao at 163 dot com
2021-10-06 10:13 ` [Bug tree-optimization/102627] " rguenth at gcc dot gnu.org
2021-10-06 10:32 ` jakub at gcc dot gnu.org [this message]
2021-10-06 10:42 ` [Bug rtl-optimization/102627] [11/12 Regression] " jakub at gcc dot gnu.org
2021-10-07 19:54 ` vmakarov at gcc dot gnu.org
2021-10-08 16:54 ` cvs-commit at gcc dot gnu.org
2021-10-11 8:32 ` [Bug rtl-optimization/102627] [11 " jakub at gcc dot gnu.org
2021-10-14 16:11 ` cvs-commit at gcc dot gnu.org
2021-10-14 16:15 ` vmakarov at gcc dot gnu.org
2021-10-22 20:11 ` hjl.tools at gmail 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-102627-4-CS8qH41FKt@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).