This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug preprocessor/21250] [4.1 Regression] line number 0 for <built-in> causes GAS to complain


------- Additional Comments From ppluzhnikov at charter dot net  2005-09-15 23:31 -------
The line '#0 <built-in>' causes trouble for other tools that work with 
the output from 'gcc -E'; e.g. edgcpfe refuses to parse it:

$ gcc -E - < /dev/null > junk.i && edgcpfe --c junk.i
"<stdin>", line 1: error: invalid line number
  # 0 "<built-in>"
    ^

1 error detected in the compilation of "junk.i".

What is the problem of emitting '#1 <built-in>' anyway?
Since neither corresponds to a "real" line number, it's not clear what
advantage '#0' has, especially if it is to be suppressed in the output.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppluzhnikov at charter dot
                   |                            |net


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21250


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]