This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: gcc 3.3: long long bug?

From: Andreas Schwab <schwab at suse dot de>
To: Eric Botcazou <ebotcazou at libertysurf dot fr>
Cc: "Lev Assinovsky" <LAssinovsky at algorithm dot aelita dot com>,<gcc-bugs at gcc dot gnu dot org>, <gcc-help at gcc dot gnu dot org>
Date: Mon, 07 Apr 2003 15:16:14 +0200
Subject: Re: gcc 3.3: long long bug?
References: <3F6F4712B759A34ABD453A8B39C10D624801F8@bagman.edm.com><200304071343.19074.ebotcazou@libertysurf.fr><jehe9ao65v.fsf@sykes.suse.de><200304071506.34922.ebotcazou@libertysurf.fr>

Eric Botcazou <ebotcazou at libertysurf dot fr> writes:

|> > That should not be needed.
|> 
|> Then there is some confusion on the compiler's side as to which constants 
|> should be accepted in which mode because there is no warning with -std=c99.

Note that the OP talked about C++, which does not have long long
officially.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab at suse dot de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

References:
- gcc 3.3: long long bug?
  - From: Lev Assinovsky
- Re: gcc 3.3: long long bug?
  - From: Eric Botcazou
- Re: gcc 3.3: long long bug?
  - From: Andreas Schwab
- Re: gcc 3.3: long long bug?
  - From: Eric Botcazou

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]