public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.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 05:06:00 -0000 [thread overview] Message-ID: <20021007120601.9789.qmail@sources.redhat.com> (raw) The following reply was made to PR preprocessor/8139; it has been noted by GNATS. From: Richard Henderson <rth@redhat.com> To: Neil Booth <neil@daikokuya.co.uk> Cc: Philippe RIBET <philippe_ribet@hotmail.com>, 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 04:57:15 -0700 On Mon, Oct 07, 2002 at 11:17:48AM +0100, Neil Booth wrote: > But what is defining this macro? GCC, or your system? Gcc does not provide <stdint.h>; glibc does. > I don't think it really matters, though. It does, because... > 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. ... the whole point of this excercise is to get proper typing of these constants. If "int" is 64-bit, for instance, then you most certainly do not want L or LL appended. It's a glibc bug. r~
next reply other threads:[~2002-10-07 12:06 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-10-07 5:06 Richard Henderson [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-07 3:26 Neil Booth 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=20021007120601.9789.qmail@sources.redhat.com \ --to=rth@redhat.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: 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).