public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: gbeauchesne@mandrakesoft.com To: gcc-gnats@gcc.gnu.org Subject: c++/10278: ICE in parser Date: Mon, 31 Mar 2003 14:46:00 -0000 [thread overview] Message-ID: <20030331143411.6127.qmail@sources.redhat.com> (raw) >Number: 10278 >Category: c++ >Synopsis: ICE in parser >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Mon Mar 31 14:36:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Gwenole Beauchesne >Release: GNU C++ version 3.2.3 20030329 (prerelease) >Organization: >Environment: i686-pc-linux-gnu >Description: As a user reported in <http://gcc.gnu.org/ml/gcc-bugs/2003-03/msg01836.html> With GNU C++ version 3.2.3 20030329 (prerelease) [gb@hp6 gcc]$ ./cc1plus ~/vrac/parens3.C int main() /home/gb/vrac/parens3.C:5: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. With GNU C++ version 3.4 20030329 (experimental) [gb@hp6 gcc]$ ./cc1plus ~/vrac/parens3.C int main() /home/gb/vrac/parens3.C:5: error: expected identifier /home/gb/vrac/parens3.C:5: internal compiler error: tree check: expected identifier_node, have error_mark in lookup_label, at cp/decl.c:4770 Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://gcc.gnu.org/bugs.html> for instructions. This is a regression from gcc version 2.95.4 20011002 (Debian prerelease) gcc version 2.96 20000731 (Mandrake Linux 9.1 2.96-0.82mdk, aka 2.96-RH 110) Also fails with 3.0.4 >How-To-Repeat: /* { dg-do compile } */ int main(void) { char x, y; if ('A' == x) && ('B' == y)) { } /* { error "parse error" } */ if (x == 'A') && (y == 'B')) { } /* { error "parse error" } */ } >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-03-31 14:36 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030331143411.6127.qmail@sources.redhat.com \ --to=gbeauchesne@mandrakesoft.com \ --cc=gcc-gnats@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).