public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/114793] wrong code at -O1 with "-fschedule-insns2 -fselective-scheduling2" on x86_64-linux-gnu (the generated code hangs)
Date: Sun, 21 Apr 2024 15:43:22 +0000 [thread overview]
Message-ID: <bug-114793-4-gBzIfhM7M2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114793-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114793
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jh at suse dot cz
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2024-04-21
Version|unknown |14.0
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Zhendong Su from comment #0)
> It seems to be a recent regression as it does not reproduce with 13.2 and
> earlier.
>
> Compiler Explorer: https://godbolt.org/z/b3cc1MqP9
>
> [538] % 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/14.0.1/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
> Thread model: posix
> Supported LTO compression algorithms: zlib
> gcc version 14.0.1 20240421 (experimental) (GCC)
> [539] %
> [539] % gcctk -O0 small.c
> [540] % ./a.out
> [541] %
> [541] % gcctk -O1 -fschedule-insns2 -fselective-scheduling2 small.c
> [542] % timeout -s 9 10 ./a.out
> Killed
> [543] %
> [543] % cat small.c
> int printf(const char *, ...);
> volatile int a;
> int b, c, d = 1, e, f;
> int main() {
> int g = 1;
> for (; b; b -= d)
> g = e;
> for (; c < 2; c++) {
> if (g) {
> if (!d)
> printf("%d", f);
> continue;
> }
> a;
> }
> return 0;
> }
This is caused by r14-2712.
next prev parent reply other threads:[~2024-04-21 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 11:47 [Bug tree-optimization/114793] New: " zhendong.su at inf dot ethz.ch
2024-04-21 11:54 ` [Bug tree-optimization/114793] " zhendong.su at inf dot ethz.ch
2024-04-21 15:43 ` hjl.tools at gmail dot com [this message]
2024-04-21 16:03 ` [Bug tree-optimization/114793] [14 Regression] " hjl.tools at gmail dot com
2024-04-22 7:17 ` jakub at gcc dot gnu.org
2024-05-07 7:45 ` [Bug tree-optimization/114793] [14/15 " 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-114793-4-gBzIfhM7M2@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).