public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: aj@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9569: 8 bytes seems to long for long long int Date: Tue, 04 Feb 2003 18:36:00 -0000 [thread overview] Message-ID: <20030204183601.7993.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9569; it has been noted by GNATS. From: Falk Hueffner <falk.hueffner@student.uni-tuebingen.de> To: aj@gcc.gnu.org Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, stefaandr@hotmail.com, gcc-gnats@gcc.gnu.org Subject: Re: c/9569: 8 bytes seems to long for long long int Date: 04 Feb 2003 17:09:21 +0100 aj@gcc.gnu.org writes: > Synopsis: 8 bytes seems to long for long long int > > Responsible-Changed-From-To: unassigned->aj > Responsible-Changed-By: aj > Responsible-Changed-When: Tue Feb 4 14:37:46 2003 > Responsible-Changed-Why: > Taking it. > State-Changed-From-To: open->closed > State-Changed-By: aj > State-Changed-When: Tue Feb 4 14:37:46 2003 > State-Changed-Why: > The program is broken, add LL to the constant to get > a long long constant. Huh? The C standard says: "The type of an integer constant is the first of the corresponding list in which its value can be represented." That would make the constant long long without any suffixes. The C++ standard doesn't have long long at all, but I would think the same semantics should be applied here, anything else would be silly. -- Falk
next reply other threads:[~2003-02-04 18:36 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 18:36 Falk Hueffner [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-06 7:36 Segher Boessenkool 2003-02-06 7:06 Neil Booth 2003-02-06 0:16 Joseph S. Myers 2003-02-06 0:06 Falk Hueffner 2003-02-05 23:46 Neil Booth 2003-02-05 22:56 Joseph S. Myers 2003-02-05 21:06 Neil Booth 2003-02-04 14:37 aj 2003-02-04 14:36 Andreas Jaeger 2003-02-04 13:36 stefaandr
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=20030204183601.7993.qmail@sources.redhat.com \ --to=falk.hueffner@student.uni-tuebingen.de \ --cc=aj@gcc.gnu.org \ --cc=gcc-prs@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).