Mail Archives: djgpp-workers/2001/05/13/09:21:56
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.
- Raw text -