public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/107711] ICE with -fanalyzer with -Wunused-macros since r13-4073-gd8aba860b34203 Date: Wed, 16 Nov 2022 21:15:31 +0000 [thread overview] Message-ID: <bug-107711-4-covR3NimX7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107711-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107711 David Malcolm <dmalcolm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|internal compiler error: |ICE with -fanalyzer with |Segmentation fault |-Wunused-macros since | |r13-4073-gd8aba860b34203 Status|UNCONFIRMED |ASSIGNED Last reconfirmed| |2022-11-16 Ever confirmed|0 |1 --- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> --- Thanks! That's really helpful; I can reproduce it now, using just: gcc/testsuite/gcc.dg/analyzer/named-constants-via-macros.c with: -fanalyzer -Wunused-macros Presumably started with r13-4073-gd8aba860b34203. Debugging it now...
next prev parent reply other threads:[~2022-11-16 21:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 0:33 [Bug analyzer/107711] New: internal compiler error: Segmentation fault urs at akk dot org 2022-11-16 14:41 ` [Bug analyzer/107711] " dmalcolm at gcc dot gnu.org 2022-11-16 15:26 ` urs at akk dot org 2022-11-16 15:50 ` dmalcolm at gcc dot gnu.org 2022-11-16 15:54 ` dmalcolm at gcc dot gnu.org 2022-11-16 19:41 ` urs at akk dot org 2022-11-16 19:50 ` urs at akk dot org 2022-11-16 21:15 ` dmalcolm at gcc dot gnu.org [this message] 2022-11-16 22:45 ` [Bug analyzer/107711] [13 Regression] ICE with "-fanalyzer -Wunused-macros" since r13-4073-gd8aba860b34203 cvs-commit at gcc dot gnu.org 2022-11-16 23:18 ` dmalcolm at gcc dot gnu.org 2022-11-17 3:07 ` dmalcolm at gcc dot gnu.org 2022-11-17 17:36 ` cvs-commit at gcc dot gnu.org 2022-11-17 17:36 ` dmalcolm at gcc dot gnu.org 2022-11-28 22:24 ` pinskia 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-107711-4-covR3NimX7@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).