public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rassahah@neofonie.de To: gcc-gnats@gcc.gnu.org Subject: c/9262: gcc-3.4 segfaults on false case label Date: Fri, 10 Jan 2003 16:46:00 -0000 [thread overview] Message-ID: <20030110164043.901.qmail@sources.redhat.com> (raw) >Number: 9262 >Category: c >Synopsis: gcc-3.4 segfaults on false case label >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Jan 10 08:46:02 PST 2003 >Closed-Date: >Last-Modified: >Originator: Rasmus Hahn >Release: gcc-3.4-cvs 20030109 (experimental) >Organization: >Environment: i686-pc-linux-gnu Thread model: posix >Description: gcc aborts with segfault after a parse error. Seems new since gcc-3.3: output: $ gcc x.c x.c: In function `main': x.c:5: error: parse error before "case" x.c:3: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. $ >How-To-Repeat: x.c: int main () { switch (3) case 3: 1, /* note comma! */ case 4: 2; } >Fix: always write correct c-programs! This is better anyway. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-10 16:46 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-10 16:46 rassahah [this message] 2003-01-10 17:10 bangerth
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=20030110164043.901.qmail@sources.redhat.com \ --to=rassahah@neofonie.de \ --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).