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/103724] [9/10/11/12 Regression] invalid warning: iteration 7 invokes undefined behavior Date: Sat, 18 Dec 2021 09:08:18 +0000 [thread overview] Message-ID: <bug-103724-4-5tZWEVUNNg@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103724-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103724 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |9.5 Status|UNCONFIRMED |NEW Known to fail| |6.3.0, 6.4.0, 7.1.0 Ever confirmed|0 |1 Last reconfirmed| |2021-12-18 Known to work| |5.5.0, 6.1.0, 6.2.0 Summary|invalid warning: iteration |[9/10/11/12 Regression] |7 invokes undefined |invalid warning: iteration |behavior |7 invokes undefined | |behavior --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Confirmed. GCC is completely unrolling this loop and then not knowing that b is 8 warns about it. Though I do find it interesting how 6.2.0 doesn't warn but 6.3.0 does.
next prev parent reply other threads:[~2021-12-18 9:08 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-15 3:05 [Bug c/103724] New: warning f.heckenbach@fh-soft.de 2021-12-15 3:11 ` [Bug c/103724] invalid warning: iteration 7 invokes undefined behavior f.heckenbach@fh-soft.de 2021-12-18 9:08 ` pinskia at gcc dot gnu.org [this message] 2021-12-28 19:53 ` [Bug tree-optimization/103724] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-01-18 14:07 ` rguenth at gcc dot gnu.org 2022-01-20 3:34 ` f.heckenbach@fh-soft.de 2022-03-09 13:36 ` rguenth at gcc dot gnu.org 2022-03-09 15:22 ` f.heckenbach@fh-soft.de 2022-05-27 9:46 ` [Bug tree-optimization/103724] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:47 ` jakub at gcc dot gnu.org 2022-12-20 13:31 ` rguenth at gcc dot gnu.org 2023-07-07 10:41 ` [Bug tree-optimization/103724] [11/12/13/14 " 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-103724-4-5tZWEVUNNg@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).