public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sebor@roguewave.com
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/8594: warning on a long long preprocessor constant
Date: Thu, 21 Nov 2002 11:06:00 -0000	[thread overview]
Message-ID: <20021115191712.6354.qmail@sources.redhat.com> (raw)


>Number:         8594
>Category:       preprocessor
>Synopsis:       warning on a long long preprocessor constant
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Nov 15 11:26:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     sebor@roguewave.com
>Release:        gcc 3.2
>Organization:
>Environment:

>Description:
The preprocessor gives a warning for a long long preprocessor constant in -pedantic mode despite the -Wno-long-long option.
Unless there is another way to suppress the warning I consider it a bug, since the compiler does not diagnose other uses of long long with the same combination of options. I would expect -Wno-long-long to suppress any diagnostics from all stages of translation.

Thanks
Martin

$ cat t.cpp; gcc --version; gcc -Wno-long-long -c -pedantic t.cpp
#define X 1LL

#if X == 1
#endif

gcc (GCC) 3.2
Copyright (C) 2002 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

t.cpp:3:5: warning: too many 'l' suffixes in integer constant
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-11-15 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 11:06 sebor [this message]
2002-11-21 11:11 zack

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=20021115191712.6354.qmail@sources.redhat.com \
    --to=sebor@roguewave.com \
    --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: link
Be 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).