"new" warnings on alphaev6-unknown-linux-gnu

[Joseph S. Myers]

On Fri, 13 Apr 2001, Kaveh R. Ghazi wrote:

> Yes that's probably what I'll do.  I can elide warn_traditional in
> c-parse.in:SAVE_WARN_FLAGS/RESTORE_WARN_FLAGS, although I regret the
> loss of the other traditional warnings.  It probably doesn't hurt us
> since __extension__ blocks won't compile on ISO C compilers either.

In principle, we ought to have an __unextension__ which counteracts the
effect of an immediately surrounding __extension__ - so that a macro with
non-standard constructs can use __extension__, then surround the macro
parameters with __unextension__ so that bad usages in macro arguments
still get detected.  (This would require counting the nesting of
__extension__ and __unextension__, since if the whole macro call were
inside __extension__ in the user's program, the __unextension__ in the
macro definition should not remove the effect of the user's
__extension__.)

-- 
Joseph S. Myers
jsm28@cam.ac.uk