This is the mail archive of the gcc@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: Can the gcc 3.x code be cleaned up to avoid unnecessary warning m essages?



Neil Booth replied (in part):
> > 	operands being signed in ANSI C and unsigned in traditional.
>
> These are unavoidable.

Here's another one that may be difficult to fix:

c-parse.y: In function `yyprint':
c-parse.y:3061: warning: ANSI C does not support the `ll' length modifier
c-parse.y:3061: warning: ANSI C does not support the `ll' length modifier

excerpt from c-parse.c:
if HOST_BITS_PER_WIDE_INT == HOST_BITS_PER_LONG
                 " 0x%lx%016lx",
#else
                 " 0x%llx%016llx",
[...]

Is there a higher level GCC implementation goal that it should compile in
ANSI mode without complaint?


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