public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Lev Assinovsky" <LAssinovsky@algorithm.aelita.com>
To: "A.R. Ashok Kumar" <ashokar@sankhya.com>
Cc: "Andreas Schwab" <schwab@suse.de>,
	"Eric Botcazou" <ebotcazou@libertysurf.fr>,
	<gcc-help@gcc.gnu.org>
Subject: RE: gcc 3.3: long long bug?
Date: Mon, 07 Apr 2003 13:43:00 -0000	[thread overview]
Message-ID: <3F6F4712B759A34ABD453A8B39C10D624802C5@bagman.edm.com> (raw)

No I meant MSVC 6.2 on Windows.
Yes, it works without any suffixes 
with 3.2 on Unix.
Also this:
const long long n =  100000000 * 1000000000;

works with 3.3 on Unix either. 

----
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 5:35 PM
> To: Lev Assinovsky
> Cc: Andreas Schwab; Eric Botcazou; gcc-help@gcc.gnu.org
> Subject: RE: gcc 3.3: long long bug?
> 
> 
> Hi,
> 
> > No, what was the reason to change the behavior of 3.2?
> > We developing the portable application which should work
> > in Windows 2000 also.
> > There is an automatic recognition of long long constants in 
> MSVC though you can 
> > add i64 suffix.
> > With 3.3 I have to write:
> > const long long n =
> > #ifdef WIN32
> > 34359738368
> > #else
> > 34359738368LL
> > #endif
> > ;
> > 
> > Not nice, right?
> 
>   Is gcc3.3 for Win32 gives error for the following statement?
> 
>     const long long n = 34359738368LL;
> 
>   If so, it is not nice behaviour. Does it work for gcc 3.2 ?
> 
> - AshokA -
> 
> 
> 

             reply	other threads:[~2003-04-07 13:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 13:43 Lev Assinovsky [this message]
2003-04-07 14:12 ` Andreas Schwab
  -- 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 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 13:08 Lev Assinovsky
2003-04-07 13:13 ` A.R. Ashok Kumar
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=3F6F4712B759A34ABD453A8B39C10D624802C5@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).