public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/8139: Bad new INT64_C macro
Date: Mon, 07 Oct 2002 03:26:00 -0000	[thread overview]
Message-ID: <20021007102603.7473.qmail@sources.redhat.com> (raw)

The following reply was made to PR preprocessor/8139; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: Philippe RIBET <philippe_ribet@hotmail.com>
Cc: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
	nobody@gcc.gnu.org
Subject: Re: preprocessor/8139: Bad new INT64_C macro
Date: Mon, 7 Oct 2002 11:17:48 +0100

 Philippe RIBET wrote:-
 
 > >What is the new definition?  What is this macro?
 > 
 > Old macro was:
 > 
 > # if __WORDSIZE == 64
 > #  define INT64_C(c)    c ## L
 > # else
 > #  define INT64_C(c)    c ## LL
 > # endif
 > 
 > New macro is:
 > #define INT64_C(val) (INT_LEAST64_MAX-INT_LEAST64_MAX+(val))
 
 But what is defining this macro?  GCC, or your system?  I don't
 think it really matters, though.
 
 Remember that with the new macro the token does not have L or LL
 appended, and therefore has type int (before promotions) in an
 arithmetic expression.  This is what is causing the warning -
 the integer is too big.  You should probably add L or LL as
 appropriate to your constants.
 
 Neil.


             reply	other threads:[~2002-10-07 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  3:26 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-07  5:06 Richard Henderson
2002-10-07  3:16 Neil Booth
2002-10-07  2:06 Philippe RIBET
2002-10-05  2:28 neil
2002-10-04 15:16 Neil Booth
2002-10-04  2:26 philippe_ribet

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=20021007102603.7473.qmail@sources.redhat.com \
    --to=neil@daikokuya.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).