public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Peter Schmid <schmid@snake.iap.physik.tu-darmstadt.de> To: gcc-gnats@gcc.gnu.org Subject: c++/2744: @ causes ice in read_token Date: Sat, 05 May 2001 06:06:00 -0000 [thread overview] Message-ID: <200105051400.QAA29082@snake.iap.physik.tu-darmstadt.de> (raw) >Number: 2744 >Category: c++ >Synopsis: @ causes ice in read_token >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Sat May 05 06:06:01 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Peter Schmid >Release: 3.0 20010503 (prerelease) >Organization: TU Darmstadt >Environment: System: Linux kiste 2.4.3 #35 Sat Mar 31 22:08:25 CEST 2001 i686 unknown Architecture: i686 SuSE 7.1 Glibc 2.2 GNU ld version 2.11.90.0.4 (with BFD 2.11.90.0.4) host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-long-long --enable-languages=c,c++,f77,objc : (reconfigured) ../gcc/configure --enable-shared --disable-nls --enable-threads=posix --enable-long-long --enable-languages=c,c++,f77,objc : (reconfigured) >Description: A stray @ causes an ice in read_token, at cp/spew.c:363. If I put a @ in a c file, gcc does not crash. >How-To-Repeat: Source code t.C @ Compiling t.C g++ -c -W -Wall t.C -save-temps t.C:1: Internal compiler error in read_token, at cp/spew.c:363 Please submit a full bug report, with preprocessed source if appropriate. See <URL: http://www.gnu.org/software/gcc/bugs.html > for instructions. cp t.C t.c Compiling t.c gcc -c -W -Wall t.c t.c:1: syntax error at '@' token Preprocessed source code t.ii # 1 "t.C" @ >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2001-05-05 6:06 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=200105051400.QAA29082@snake.iap.physik.tu-darmstadt.de \ --to=schmid@snake.iap.physik.tu-darmstadt.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).