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 fortran/94978] [8/9/10/11 Regression] Bogus warning "Array reference at (1) out of bounds in loop beginning at (2)" Date: Mon, 18 May 2020 08:56:39 +0000 [thread overview] Message-ID: <bug-94978-4-Qctq8muBv9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94978-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94978 Thomas Koenig <tkoenig at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Blocks| |90302 Status|UNCONFIRMED |NEW Last reconfirmed| |2020-05-18 CC| |tkoenig at gcc dot gnu.org --- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> --- Two ways to fix this: When checking for outer do loops, also check if the inner one will be executed at all. Or PR 90302, which is looking more attractive than ever. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90302 [Bug 90302] Implement __builtin_warning
next prev parent reply other threads:[~2020-05-18 8:56 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-05-06 23:22 [Bug fortran/94978] New: " foreese at gcc dot gnu.org 2020-05-06 23:26 ` [Bug fortran/94978] " foreese at gcc dot gnu.org 2020-05-07 7:28 ` rguenth at gcc dot gnu.org 2020-05-18 8:56 ` tkoenig at gcc dot gnu.org [this message] 2020-07-26 7:58 ` tkoenig at gcc dot gnu.org 2020-11-02 20:11 ` anlauf at gcc dot gnu.org 2021-01-14 8:42 ` rguenth at gcc dot gnu.org 2021-04-16 16:22 ` tkoenig at gcc dot gnu.org 2021-05-14 9:53 ` [Bug fortran/94978] [9/10/11/12 " jakub at gcc dot gnu.org 2021-06-01 8:17 ` rguenth at gcc dot gnu.org 2022-05-27 9:42 ` [Bug fortran/94978] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:40 ` jakub at gcc dot gnu.org 2023-07-07 10:37 ` [Bug fortran/94978] [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-94978-4-Qctq8muBv9@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).