This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Question on -Werror usage in Makefiles...


> Joern - would you please test this patch on an SH target and let us
> know if there are any remaining "uninitialized" warnings in libgcc2.c?
> 
> 		Thanks,
> 		--Kaveh
> 
> 
> 2003-11-07  Kaveh R. Ghazi  <ghazi@caip.rutgers.edu>
> 
> 	* libgcc2.c (__negdi2, __addvsi3, __addvdi3, __subvsi3, __subvdi3,
> 	__mulvsi3, __negvsi2, __negvdi2, __mulvdi3, __lshrdi3, __ashldi3,
> 	__ashrdi3, __ffsDI2, __muldi3, __clzDI2, __ctzDI2, __parityDI2,
> 	__udivmoddi4, __divdi3, __moddi3, __cmpdi2, __ucmpdi2,
> 	__fixunstfDI, __fixunsxfDI, __fixunsdfDI, __fixunssfDI,
> 	__floatdixf, __floatditf, __floatdidf, __floatdisf, __gcc_bcmp):
> 	Const-ify and/or initialize automatic variables at declaration.

Sorry for the delay, for some unknown reason I didn't get a personal
copy of your email.

I've tried your patch in the sources of yesterday - with the objdump.c
breakage reverted - and indeed, there appear to be no libgcc2 warnings
left now.

A few warnings from other components of the compiler and from C / libobjc
libraries remain, though... 722 in my build, to be exact ;-)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]