public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/114691] New: [11/12/13/14 Regression] Bogus ignoring loop annotation warning Date: Thu, 11 Apr 2024 10:08:42 +0000 [thread overview] Message-ID: <bug-114691-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114691 Bug ID: 114691 Summary: [11/12/13/14 Regression] Bogus ignoring loop annotation warning Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: ice-on-valid-code Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org CC: jakub at gcc dot gnu.org, jason at gcc dot gnu.org, pinskia at gcc dot gnu.org, ppalka at gcc dot gnu.org, sjames at gcc dot gnu.org, webrown.cpp at gmail dot com Depends on: 114409 Target Milestone: --- +++ This bug was initially created as a clone of Bug #114409 +++ As the PR114409 initially reported P1 bug is now fixed, I'm cloning it for the https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114409#c10 regression. int foo (int); void qux (int x) { #pragma GCC ivdep while (int y = foo (x)) ++y; } With no options this didn't emit any warnings e.g. in r200000 (i.e. in GCC 4.9), while it emits pr114409-2.C:7:24: warning: ignoring loop annotation warning in r220000 (i.e. in GCC 5+). Can't bisect easily, because in various revisions in between it ICEs on ANNOTATE_EXPR. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114409 [Bug 114409] [14 Regression] ICE after adding novector pragmas (internal compiler error: in tsubst_expr, at cp/pt.cc:21794) since r14-4229-g9c62af101e11e1cce573c2b3d2e18b403412dbc8
next reply other threads:[~2024-04-11 10:08 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-11 10:08 jakub at gcc dot gnu.org [this message] 2024-04-11 10:09 ` [Bug c++/114691] " jakub at gcc dot gnu.org 2024-04-11 10:11 ` jakub at gcc dot gnu.org 2024-04-12 18:55 ` cvs-commit at gcc dot gnu.org 2024-04-12 18:55 ` [Bug c++/114691] [11/12/13 " jakub at gcc dot gnu.org 2024-04-21 4:09 ` cvs-commit at gcc dot gnu.org 2024-04-23 6:44 ` [Bug c++/114691] [11/12 " jakub 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-114691-4@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).