public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: ted@arraycomm.com To: gcc-gnats@gcc.gnu.org Subject: preprocessor/7022: #line in .i files is broken in gcc 3.1 Date: Thu, 13 Jun 2002 12:36:00 -0000 [thread overview] Message-ID: <20020613192919.22813.qmail@sources.redhat.com> (raw) >Number: 7022 >Category: preprocessor >Synopsis: #line in .i files is broken in gcc 3.1 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Thu Jun 13 12:36:04 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Ted Merrill >Release: gcc-3.1 >Organization: >Environment: Sparc solaris >Description: gcc-3.1 chokes on #line directive in a pre-processed (.i) file. This worked in gcc-3.0.4 and earlier. We make heavy use of a tool that modifies C code after passing through the preprocessor. We can modify the tool to work around this bug (by producing the # number format...) but it would still be nice to get this fixed. >How-To-Repeat: E.g. the following: #line 1 "mainfile.c" int x; #line 23 "specialfile" int y; produces the following (with -v option): Reading specs from /opt/local/gnu/gcc3-64/lib/gcc-lib/sparc64-sun-solaris2.8/3.1/specs Configured with: ../gcc-3.1/configure --prefix=/opt/local/gnu/gcc3-64 --enable-languages=c,c++ --enable-threads=posix --verbose --enable-long-long --enable-shared --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --with-cpu=ultrasparc --disable-nls sparc64-sun-solaris2.8 Thread model: posix gcc version 3.1 /opt/local/gnu/gcc3-64/lib/gcc-lib/sparc64-sun-solaris2.8/3.1/cc1 -fpreprocessed ilinebug2.i -quiet -dumpbase ilinebug2.i -version -o /var/tmp//ccILGXxb.s GNU CPP version 3.1 (cpplib) (sparc ELF) GNU C version 3.1 (sparc64-sun-solaris2.8) compiled by GNU C version 3.1. ilinebug2.i:1: syntax error at '#' token ilinebug2.i:1: parse error before numeric constant ilinebug2.i:4: syntax error at '#' token >Fix: I think there are two areas in the source code that need a fix. Most importantly, there is some problem with generic #line handling that i have not figured out. Secondarily, there is code to peek at the first line of a file for a # <number> directive, which is clearly broken since it does not check for #line ... if this never got fixed it would be no big deal. >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-06-13 19:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-06-13 12:36 ted [this message] 2002-06-13 13:29 neil 2002-06-13 13:36 Neil Booth 2002-06-13 13:46 Ted Merrill
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=20020613192919.22813.qmail@sources.redhat.com \ --to=ted@arraycomm.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).