From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: "A.R. Ashok Kumar" <ashokar@sankhya.com>,
"Andreas Schwab" <schwab@suse.de>
Cc: "Eric Botcazou" <ebotcazou@libertysurf.fr>, <gcc-help@gcc.gnu.org>
Subject: RE: gcc 3.3: long long bug?
Date: Mon, 07 Apr 2003 13:08:00 -0000 [thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D62480284@bagman.edm.com> (raw)
No, sizeof (long long) is 8 in my system.
----
Lev Assinovsky
Aelita Software Corporation
O&S Core Division, Programmer
ICQ# 165072909
> -----Original Message-----
> From: A.R. Ashok Kumar [mailto:ashokar@sankhya.com]
> Sent: Monday, April 07, 2003 4:30 PM
> To: Andreas Schwab
> Cc: Eric Botcazou; Lev Assinovsky; gcc-help@gcc.gnu.org
> Subject: Re: gcc 3.3: long long bug?
>
>
> Hi,
>
> > |> > const long long n = 34359738368; // 2^35
> > |> >
> > |> > Got:
> > |> > max.cpp:1: error: integer constant is too large for "long" type
> > |>
> > |> Append "LL" to the constant.
> >
> > That should not be needed.
>
> Size for type "long long" may be only 32-bit in your
> system. Since it
> is 35-bit number, it gives error.
>
> You can check the size of "long long" type in your system,
> by printing
> sizeof(long long).
>
> Best Wishes,
> AshokA
>
>
next reply other threads:[~2003-04-07 13:08 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-07 13:08 Lev Assinovsky [this message]
2003-04-07 13:13 ` A.R. Ashok Kumar
-- strict thread matches above, loose matches on Subject: below --
2003-04-07 14:44 Lev Assinovsky
2003-04-07 14:41 Lev Assinovsky
2003-04-07 14:58 ` Andreas Schwab
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 13:33 Lev Assinovsky
2003-04-07 13:15 Lev Assinovsky
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 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
2003-04-07 13:11 ` Andreas Schwab
2003-04-07 13:11 ` Eric Botcazou
2003-04-07 13:16 ` Andreas Schwab
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=3F6F4712B759A34ABD453A8B39C10D62480284@bagman.edm.com \
--to=lassinovsky@algorithm.aelita.com \
--cc=ashokar@sankhya.com \
--cc=ebotcazou@libertysurf.fr \
--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).