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] [14 Regression] wrong code at -O1 with "-fschedule-insns2 -fselective-scheduling2" on x86_64-linux-gnu (the generated code hangs)
Date: Sun, 21 Apr 2024 16:03:43 +0000 [thread overview]
Message-ID: <bug-114793-4-ym2CszWgG9@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
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Zhendong Su from comment #1)
> The following reproducer is different, but perhaps is the same or related.
>
> Compiler Explorer: https://godbolt.org/z/411rzMP1n
>
> [588] % 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)
> [589] %
> [589] % gcctk -O1 -fno-tree-forwprop -fselective-scheduling2
> -fschedule-insns2 -fsel-sched-pipelining small.c
> [590] % ./a.out
> Aborted
> [591] %
> [591] % cat small.c
> int printf(const char *, ...);
> int a, d, g, h;
> volatile int b = 1;
> static unsigned c = 1;
> char e, f = 1, i;
> static int j() {
> int k, l = g, m = 1 << l, n = -e, o = -1 % ((f && 1) ^ i), p = ~n - o;
> if (m) {
> int q, s, t, r = 1 % (((1 % f) & (~e | c)) ^ b);
> q = f;
> s = i;
> t = e;
> f = -b;
> k = f;
> d = -1;
> u:
> e = 0 & b;
> if (i > f)
> if (!b)
> goto v;
> if (d > t)
> __builtin_abort();
> if (b < 1 || !d || !c) {
> printf("%d\n", i);
> f = ((i | b) & (k - r)) << (e << ~t ^ q) << s;
> goto u;
> }
> if (i)
> f = q;
> v:
> i = n & o & l;
> printf("%ld\n", (long)t);
> }
> i = p;
> return h;
> }
> int main() {
> for (; a < 3; a++)
> j();
> return 0;
> }
This is caused by r14-2524.
next prev parent reply other threads:[~2024-04-21 16:03 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
2024-04-21 16:03 ` hjl.tools at gmail dot com [this message]
2024-04-22 7:17 ` [Bug tree-optimization/114793] [14 Regression] " 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-ym2CszWgG9@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).