public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/99323] [9/10/11 Regression] ICE in add_hint, at diagnostic-show-locus.c:2234 since r8-379-gd1b5f5cc3cfd148e Date: Tue, 02 Mar 2021 10:12:58 +0000 [thread overview] Message-ID: <bug-99323-4-TlipDFeH5f@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99323-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99323 --- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> --- Slightly reduced test-case: $ cat x.c typedef struct { } REFERENCE; #define LIM2() LIM1() #define LIM3() LIM2() LIM2() LIM2() LIM2() LIM2() LIM2() #define LIM4() \ LIM3() LIM3() LIM3() LIM3() LIM3() LIM3() LIM3() LIM3() LIM3() LIM3() #define LIM5() \ LIM4() LIM4() LIM4() LIM4() LIM4() LIM4() LIM4() LIM4() LIM4() LIM4() #define LIM1() DEF(), REFERENCE references[] = {LIM5()}
next prev parent reply other threads:[~2021-03-02 10:12 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-01 17:03 [Bug c/99323] New: [9/10/11 Regression] ICE in add_hint, at diagnostic-show-locus.c:2234 gscfq@t-online.de 2021-03-02 7:37 ` [Bug c/99323] " rguenth at gcc dot gnu.org 2021-03-02 9:51 ` [Bug c/99323] [9/10/11 Regression] ICE in add_hint, at diagnostic-show-locus.c:2234 since r8-379-gd1b5f5cc3cfd148e marxin at gcc dot gnu.org 2021-03-02 10:12 ` marxin at gcc dot gnu.org [this message] 2021-03-02 14:31 ` dmalcolm at gcc dot gnu.org 2021-03-02 20:47 ` cvs-commit at gcc dot gnu.org 2021-03-02 20:50 ` [Bug c/99323] [9/10 " dmalcolm at gcc dot gnu.org 2021-04-30 8:09 ` rguenth at gcc dot gnu.org 2021-06-01 8:19 ` rguenth at gcc dot gnu.org 2022-05-27 9:44 ` [Bug c/99323] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:43 ` jakub at gcc dot gnu.org 2023-07-07 9:29 ` 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-99323-4-TlipDFeH5f@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).