This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Warning policy?
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: Warning policy?
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Wed, 06 Jan 1999 00:45:48 -0700
- cc: rth at cygnus dot com, chip at perlsupport dot com, egcs-patches at cygnus dot com, egcs at cygnus dot com, jbuck at Synopsys dot COM, mark at markmitchell dot com, pfeifer at dbai dot tuwien dot ac dot at, schwab at issan dot informatik dot uni-dortmund dot de
- Reply-To: law at cygnus dot com
In message <199901051514.KAA12156@caip.rutgers.edu>you write:
> If not, I can write an autoconf test to set __GNUC_MICRO__ if
> "GCC == 2.92".
I'd do a feature test instead of a version # test for autoconf stuff.
ie, compile a trivial program that puts an unused attribute on a label
then try to compile it. If it fails, then it's not supported.
This means that folks that build with "cc" as their stage1 compiler or
older versions of egcs would still get the warnings, but I can live with
that.
> Another option would be to simply bump the check to "GCC < 2.93" in
> gansidecl.h (with or without an actual egcs minor version number bump.)
That would be fine with me too. We could bump the version # to 2.93 if
we want.
jeff