This is the mail archive of the 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]

RE: cpplib: Nix -g3.

>-----Original Message-----
>From: Zack Weinberg [mailto:zackw@Stanford.EDU]
>Sent: 12 January 2001 04:41

>On Thu, Jan 11, 2001 at 06:54:40PM +0000, Neil Booth wrote:
>> Zack Weinberg wrote:-
>> > That too might've been something to do with.  IIRC we're supposed to
>> > spit out 
>> > 
>> > # 1 "file.c"
>> > 
>> > in between each builtin macro definition.  1 might have been 0.  This
>> > was a very long time ago.
>> Well, the nice thing is that this is the natural behaviour when you
>> remove those if statements.  It also re-preprocesses correctly with
>> -fpreprocessed, with the patch below to prevent double-initialization
>> of builtins and command line switches.  I must have got something
>> right when I moved all this stuff to cppmain.c :-)
>> As for # 1 file.c or # 0 file.c, who's the right person to ask?  If 0
>> is the line number we want, it won't be too hard to correct, I think.
>The gdb people might know.  I'd say leave it as 1 until someone

  PMFBI, but I think something I've spotted in the vxworks port might be
relevant to this issue:  _BIG_ENDIAN gets defined in one of the OS header
files, but it's also passed in the specs as a -D flag. Is this the situation
you're talking about? Because what I see for a line number is:

F:/Tornado/target/h/types/vxArch.h:46: warning: `_BIG_ENDIAN' redefined
*Initialization*:1: warning: this is the location of the previous definition

  Would that be line 0, by any chance?

The Boulder Pledge: "Under no circumstances will I ever purchase anything 
offered to me as the result of an unsolicited email message. Nor will I 
forward chain letters, petitions, mass mailings, or virus warnings to large 
numbers of others. This is my contribution to the survival of the online

This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

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