public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: andrew@andypo.net To: gcc-gnats@gcc.gnu.org Subject: other/7263: __extension__ keyword doesn't suppress warning on LL or ULL constants Date: Wed, 10 Jul 2002 08:26:00 -0000 [thread overview] Message-ID: <20020710152412.8728.qmail@sources.redhat.com> (raw) >Number: 7263 >Category: other >Synopsis: __extension__ keyword doesn't suppress warning on LL or ULL constants >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Jul 10 08:26:00 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Andrew Pollard >Release: gcc-3.2-20020710 >Organization: >Environment: System: Linux garfield.andypo.net 2.4.18-5smp #1 SMP Mon Jun 10 15:19:40 EDT 2002 i686 unknown Architecture: i686 Binutils 2.12.90.0.14 20020627 Redhat 7.3 dual processor P3 system host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: /usr/local/src/cvs/gcc/configure --prefix=/usr/local/gcc-3.2-20020710-i686-pc-linux-gnu --with-gnu-as --with-gnu-ld --enable-version-specific-runtime-libs --enable-threads=posix --with-dwarf2 --disable-shared --enable-languages=c++ >Description: The following code fragment generates a warning in gcc-3.2-20020710, where previous versions (gcc-3.1, gcc-3.0) didn't. a.c: -------------------------------------------------------- __extension__ unsigned long long foo() { return (__extension__ 0x1b27da572ef3cd86ULL); } -------------------------------------------------------- % gcc -W -Wall -Werror -ansi -pedantic -c a.c a.c:4:27: use of C99 long long integer constant Even though the constant is wrapped using __extension__ __extension__ still removes the warning on the use of the unsigned long long type. -Wno-long-long is a workaround for me at the moment. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-07-10 15:26 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20020710152412.8728.qmail@sources.redhat.com \ --to=andrew@andypo.net \ --cc=gcc-gnats@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).