From: John Love-Jensen <eljay@adobe.com>
To: Andreas Schwab <schwab@suse.de>,
Eric Botcazou <ebotcazou@libertysurf.fr>
Cc: Lev Assinovsky <LAssinovsky@algorithm.aelita.com>,
<gcc-bugs@gcc.gnu.org>, <gcc-help@gcc.gnu.org>
Subject: Re: gcc 3.3: long long bug?
Date: Mon, 07 Apr 2003 13:01:00 -0000 [thread overview]
Message-ID: <BAB6E0B9.80ED%eljay@adobe.com> (raw)
In-Reply-To: <jehe9ao65v.fsf@sykes.suse.de>
Hi Andreas,
> |> Append "LL" to the constant.
>
> That should not be needed.
The "LL" should be needed, unless a "long long" is the same size as a
"long".
The "long long" data type is an extension to the C (ISO 9989) and C++ (ISO
14882) specs. As such, automatically sizing a numeric literal to "long
long" (like how a numeric literal that's too big for an "int" becomes an
"unsigned int", and then a "long" and then an "unsigned long") could cause
problems.
Unfortunately, requiring the "LL" suffix causes other headaches.
I wonder when we'll have "long long long" (128-bit) and "long long long
long" (256-bit) numbers. With accompanying "LLL" and "LLLL" suffixes.
*sigh*
--Eljay
next prev parent reply other threads:[~2003-04-07 13:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 11:29 Lev Assinovsky
2003-04-07 11:42 ` Eric Botcazou
2003-04-07 12:15 ` Andreas Schwab
2003-04-07 12:31 ` A.R. Ashok Kumar
2003-04-07 12:42 ` Andreas Schwab
2003-04-07 13:09 ` A.R. Ashok Kumar
2003-04-07 13:13 ` Andreas Schwab
2003-04-07 13:18 ` A.R. Ashok Kumar
2003-04-07 14:28 ` Anders Ådland
2003-04-07 14:36 ` Andreas Schwab
2003-04-07 14:38 ` A.R. Ashok Kumar
2003-04-07 14:56 ` Andreas Schwab
2003-04-07 13:01 ` John Love-Jensen [this message]
2003-04-07 13:11 ` Andreas Schwab
2003-04-07 13:11 ` Eric Botcazou
2003-04-07 13:16 ` Andreas Schwab
2003-04-07 13:08 Lev Assinovsky
2003-04-07 13:13 ` A.R. Ashok Kumar
2003-04-07 13:13 Lev Assinovsky
2003-04-07 13:43 ` A.R. Ashok Kumar
2003-04-07 13:40 ` John Love-Jensen
2003-04-07 14:12 ` A.R. Ashok Kumar
2003-04-07 14:04 ` Andreas Schwab
2003-04-07 13:15 Lev Assinovsky
2003-04-07 13:33 Lev Assinovsky
2003-04-07 13:43 Lev Assinovsky
2003-04-07 14:12 ` Andreas Schwab
2003-04-07 13:43 Lev Assinovsky
2003-04-07 13:36 ` A.R. Ashok Kumar
2003-04-07 20:22 ` Ben Davis
2003-04-07 14:41 Lev Assinovsky
2003-04-07 14:58 ` Andreas Schwab
2003-04-07 14:44 Lev Assinovsky
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=BAB6E0B9.80ED%eljay@adobe.com \
--to=eljay@adobe.com \
--cc=LAssinovsky@algorithm.aelita.com \
--cc=ebotcazou@libertysurf.fr \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-help@gcc.gnu.org \
--cc=schwab@suse.de \
/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).