public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Philippe RIBET" <philippe_ribet@hotmail.com>
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 02:06:00 -0000	[thread overview]
Message-ID: <20021007090602.13857.qmail@sources.redhat.com> (raw)

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

From: "Philippe RIBET" <philippe_ribet@hotmail.com>
To: gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc: philippe_ribet@hotmail.com
Subject: Re: preprocessor/8139: Bad new INT64_C macro
Date: Mon, 07 Oct 2002 08:59:44 +0000

 >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))
 
 
 (in file include/stdint.h)
 
 This macro is part of ANSI C99 standard. It allows to specify integer 
 constant size.
 
 >I suspect the warnings are correct, but new, and that the definition
 of the macro is unchanged.
 No, definition changed.
 No, warnings are not correct as INT64_C(-3000000000) is valid code because 
 -3000000000 is valid 64bits integer.
 
 >You should probably add a U to the relevant numbers.
 ??? 'U' with negative numbers ???
 
 >Anyway, not a GCC bug.
 Is IS a GCC bug if you consider ANSI C99 standard.
 
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8139
 
 
 --
 Philippe Ribet
 
 
 
 _________________________________________________________________
 Send and receive Hotmail on your mobile device: http://mobile.msn.com
 


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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-07  2:06 Philippe RIBET [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-07  5:06 Richard Henderson
2002-10-07  3:26 Neil Booth
2002-10-07  3:16 Neil Booth
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=20021007090602.13857.qmail@sources.redhat.com \
    --to=philippe_ribet@hotmail.com \
    --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).