public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110116] [12/13/14 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: verify_gimple failed Date: Wed, 01 Nov 2023 19:22:52 +0000 [thread overview] Message-ID: <bug-110116-4-WXI8bt60E2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110116-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110116 --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Looks like this has been fixed in the meantime: tkoenig@gcc188:~> gcc -O3 small.c small.c: In function 'main': small.c:6:21: warning: iteration 2147483646 invokes undefined behavior [-Waggressive-loop-optimizations] 6 | for (b = 1; b; b++) | ~^~ small.c:6:17: note: within this loop 6 | for (b = 1; b; b++) | ^ tkoenig@gcc188:~> gcc --version gcc (GCC) 14.0.0 20231101 (experimental) [master r13-4915-g9b111debbfb] Copyright (C) 2023 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. tkoenig@gcc188:~> cat small.c unsigned char a[5]; int b, d; char c; int main() { if (d) { for (b = 1; b; b++) c &= d = 1; for (; d < 5; d++) c &= a[d]; } return 0; } Still interesting which revision fixed it.
next prev parent reply other threads:[~2023-11-01 19:22 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-04 21:24 [Bug tree-optimization/110116] New: " zhendong.su at inf dot ethz.ch 2023-06-04 22:17 ` [Bug tree-optimization/110116] [12/13/14 Regression] " pinskia at gcc dot gnu.org 2023-06-05 6:51 ` rguenth at gcc dot gnu.org 2023-11-01 19:22 ` tkoenig at gcc dot gnu.org [this message] 2023-11-02 18:29 ` [Bug tree-optimization/110116] [12/13 " tkoenig at gcc dot gnu.org 2023-12-15 12:23 ` rguenth at gcc dot gnu.org 2024-05-08 11:56 ` 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-110116-4-WXI8bt60E2@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: linkBe 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).