X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs Date: Sun, 13 May 2001 15:21:52 +0200 (MET DST) From: Hans-Bernhard Broeker X-Sender: broeker AT acp3bf To: djgpp-workers AT delorie DOT com cc: DJ Delorie Subject: Re: [PATCH] Update to compiler options for DJGPP CVS version In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Sat, 12 May 2001, Andris Pavenis wrote: > > > On Sat, 12 May 2001, DJ Delorie wrote: > > > > > > - removed -traditional. -traditional is becoming nuisance with gcc-3.0 > > > > Can you give specific examples of the problems it causes? > > > > Some time ago (perhaps 15 March CVS version) I got large number of > additional warnings we would have to deal with. As I remeber I posted > information about this in djgpp-workers list. Yes. I remember that one. 300 warnings from the libc build, over 90% of which were by of the 'traditional/K&R C interprets this differently' type, and activated by the -Wtraditional switch. But -traditional doesn't imply -Wtraditional, does it? > > To get it not compaining about command line parameters I had now to > eliminate -remap and -imacros ... from cpp specs when -traditional is > being used (like %{!traditional:-remap}). The latest one is significant > for DJGPP as it's used to get macros __DJGPP__, __DJGPP_MINOR__ Bad idea, I think. May be -traditional -no-traditional-cpp would be a better plan. Or, as you proposed, drop -traditional altogether. Using GCC style options like '-traditional', we're hardwiring the assumption that the compiler is GCC, anyway. So there's not much sense pretending the compiler is not capable of ANSI C, is there? -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.