Warning policy?

[Kaveh R. Ghazi]

 > From: Richard Henderson <rth@cygnus.com>
 > 
 > On Tue, Jan 05, 1999 at 01:43:45AM -0700, Jeffrey A Law wrote:
 > > I think a test based on the version of gcc should be sufficient to fix the
 > > problem.  Can you take care of that?
 > 
 > Not without bumping the minor version of egcs.  Otherwise
 > anything post 1.1 but older than a few days will still fail.
 > r~

	Urg.  Yes, if your stage1 compiler is a snapshot between 2.92.1
-> 2.92.33, it'll fail.  (Is this a common practice?  I would have
thought not, because if you had a problem, you wouldn't know whether the
stage1 compiler was at fault or the current snapshot was.  Obviously too
much ass-u-ME-ing :-) on my part though.)


What I need to do is test "GCC < 2.92.34".  Is there a way to check the
egcs micro version number?

	If not, I can write an autoconf test to set __GNUC_MICRO__ if
"GCC == 2.92".

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.)

Yet another option would be to somehow enable to attribute when
stage>=2, or put another way, disable the attribute when stage==1.
But I'm not sure of the easiest way to do that off the top of my head. 

		--Kaveh
--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Icon CMT Corp.