public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zhendong.su at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/107195] New: wrong code with "-O1 -fno-tree-ccp" on x86_64-linux-gnu
Date: Sun, 09 Oct 2022 13:01:53 +0000 [thread overview]
Message-ID: <bug-107195-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107195
Bug ID: 107195
Summary: wrong code with "-O1 -fno-tree-ccp" on
x86_64-linux-gnu
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: zhendong.su at inf dot ethz.ch
Target Milestone: ---
This doesn't fail with 12.2, so looks like a recent regression. Perhaps related
to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107172 or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107194?
Compiler Explorer: https://godbolt.org/z/94E6r84ra
[524] % gcctk -v
Using built-in specs.
COLLECT_GCC=gcctk
COLLECT_LTO_WRAPPER=/local/suz-local/software/local/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/13.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-trunk/configure --disable-bootstrap
--enable-checking=yes --prefix=/local/suz-local/software/local/gcc-trunk
--enable-sanitizers --enable-languages=c,c++ --disable-werror --enable-multilib
--with-system-zlib
Thread model: posix
Supported LTO compression algorithms: zlib
gcc version 13.0.0 20221009 (experimental) [master r13-3180-ge95e91eccd0] (GCC)
[525] %
[525] % gcctk -O1 small.c; ./a.out
[526] %
[526] % gcctk -O1 -fno-tree-ccp small.c
[527] % ./a.out
Aborted
[528] %
[528] % cat small.c
int a, b;
int main() {
int c = 0;
if (a)
c = 1;
c = 1 & (a && c) && b;
if (a) {
b = c;
__builtin_abort ();
}
return 0;
}
next reply other threads:[~2022-10-09 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-09 13:01 zhendong.su at inf dot ethz.ch [this message]
2022-10-09 18:59 ` [Bug tree-optimization/107195] " pinskia at gcc dot gnu.org
2022-10-09 18:59 ` [Bug tree-optimization/107195] [13 Regression] " pinskia at gcc dot gnu.org
2022-10-09 19:01 ` 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@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).