public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/35326] [4.2/4.3 regression] ICE with stray digraph token Date: Tue, 11 Nov 2008 21:06:00 -0000 [thread overview] Message-ID: <20081111210458.31775.qmail@sourceware.org> (raw) In-Reply-To: <bug-35326-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #7 from reichelt at gcc dot gnu dot org 2008-11-11 21:04 ------- The bug disappeared on mainline. The crash with the C frontend disappeared much later than the one with the C++ frontend. Therefore, I don't think that the bug has been really fixed, we are just lucky that it doesn't trigger segfaults anymore. -- reichelt at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|[4.2/4.3/4.4 regression] ICE|[4.2/4.3 regression] ICE |with stray digraph token |with stray digraph token http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35326
next prev parent reply other threads:[~2008-11-11 21:06 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-23 19:07 [Bug c++/35326] New: [4.2/4.3/4.4 " reichelt at gcc dot gnu dot org 2008-02-23 19:07 ` [Bug c++/35326] " reichelt at gcc dot gnu dot org 2008-02-24 22:07 ` rguenth at gcc dot gnu dot org 2008-03-02 21:24 ` [Bug preprocessor/35326] " reichelt at gcc dot gnu dot org 2008-03-13 15:54 ` tromey at gcc dot gnu dot org 2008-03-14 7:45 ` reichelt at gcc dot gnu dot org 2008-04-05 13:31 ` tromey at gcc dot gnu dot org 2008-04-10 6:17 ` reichelt at gcc dot gnu dot org 2008-05-19 20:47 ` jsm28 at gcc dot gnu dot org 2008-11-11 21:06 ` reichelt at gcc dot gnu dot org [this message] 2009-03-31 20:22 ` [Bug preprocessor/35326] [4.3 " jsm28 at gcc dot gnu dot org 2009-04-22 15:25 ` rguenth at gcc dot gnu dot 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=20081111210458.31775.qmail@sourceware.org \ --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).