rs6000_{init,free}_machine_status missing prototypes

Kaveh R. Ghazi ghazi@caip.rutgers.edu
Wed Jan 17 15:23:00 GMT 2001


 > I though about trying to fix up all the other compile time warnings
 > when building rs6000.c, but I do not know the official way to
 > workaround warnings like:
 > 
 >   rs6000.c:3904: warning: integer constant is unsigned in ANSI C,
 >   signed with -traditional

You're probably looking at stage1 warnings from 2.95.2.  Try looking
at stage3 instead.  GCC 3.0 doesn't warn about these unless the base
of the constant is 10.

So many people stumble on this, I probably should have submitted it
for 2.95.3.  Its not a critical fix, but it's effectively a one liner
that helps people avoid false positives.  I suppose it's probably too
late now, but...

Bernd?

http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-lex.c.diff?r1=1.66&r2=1.67
http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/invoke.texi.diff?r1=1.155&r2=1.156


--
Kaveh R. Ghazi			Engagement Manager / Project Services
ghazi@caip.rutgers.edu		Qwest Internet Solutions


More information about the Gcc-patches mailing list