This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Can the gcc 3.x code be cleaned up to avoid unnecessary warning m essages?
- From: Geoff Keating <geoffk at geoffk dot org>
- To: "Gary Funck" <gary at intrepid dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 29 May 2002 15:53:47 -0700
- Subject: Re: Can the gcc 3.x code be cleaned up to avoid unnecessary warning m essages?
- References: <PMEMKNKIFEFGJGBCJFPPOEHPCBAA.gary@intrepid.com>
"Gary Funck" <gary@intrepid.com> writes:
> 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?
Actually, there's an outstanding project, to develop a way to suppress
warnings like these in the compiler.
--
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>