public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107195] [13 Regression] wrong code with "-O1 -fno-tree-ccp" on x86_64-linux-gnu
Date: Sun, 09 Oct 2022 18:59:35 +0000 [thread overview]
Message-ID: <bug-107195-4-W6yM0eFBCP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107195-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107195
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|wrong code with "-O1 |[13 Regression] wrong code
|-fno-tree-ccp" on |with "-O1 -fno-tree-ccp" on
|x86_64-linux-gnu |x86_64-linux-gnu
Known to work| |12.2.0
Target Milestone|--- |13.0
Keywords| |wrong-code
next prev parent reply other threads:[~2022-10-09 18:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:01 [Bug tree-optimization/107195] New: " zhendong.su at inf dot ethz.ch
2022-10-09 18:59 ` [Bug tree-optimization/107195] " pinskia at gcc dot gnu.org
2022-10-09 18:59 ` pinskia at gcc dot gnu.org [this message]
2022-10-09 19:01 ` [Bug tree-optimization/107195] [13 Regression] " pinskia at gcc dot gnu.org
2022-10-10 7:24 ` rguenth at gcc dot gnu.org
2022-10-10 13:23 ` [Bug tree-optimization/107195] [13 Regression] wrong code with "-O1 -fno-tree-ccp" on x86_64-linux-gnu since r13-3090-gdf4c584c567263fd marxin at gcc dot gnu.org
2022-10-10 18:49 ` aldyh at gcc dot gnu.org
2022-10-10 18:52 ` aldyh at gcc dot gnu.org
2022-10-10 18:53 ` aldyh at gcc dot gnu.org
2022-10-11 8:31 ` cvs-commit at gcc dot gnu.org
2022-10-11 9:02 ` aldyh at gcc dot gnu.org
2022-10-12 7:48 ` marxin at gcc dot gnu.org
2022-10-21 9:29 ` cvs-commit at gcc dot gnu.org
2022-10-21 9:29 ` cvs-commit 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-107195-4-W6yM0eFBCP@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).