--- Comment #7 from lukew at radterm dot com dot au 2006-10-27 03:51
---
(In reply to comment #6)
> Subject: Re: hex and oct constants are converted to wrong type
>
> lukew at radterm dot com dot au wrote:-
>
> > > The resulting tokens compose the controlling constant expression wh
--- Comment #6 from neil at daikokuya dot co dot uk 2006-10-26 12:42
---
Subject: Re: hex and oct constants are converted to wrong type
lukew at radterm dot com dot au wrote:-
> > The resulting tokens compose the controlling constant expression which
> > is evaluated according t
--- Comment #5 from lukew at radterm dot com dot au 2006-10-26 06:45
---
(In reply to comment #3)
> Subject: Re: hex and oct constants are converted to
> wrong type
> The resulting tokens compose the controlling constant expression which
> is evaluated according to the rules of
--- Comment #4 from mhx-perl at gmx dot net 2006-04-18 13:26 ---
Subject: Re: hex and oct constants are converted to
wrong type
On 2006-04-18, at 11:22:00 -, joseph at codesourcery dot com wrote:
> 142) Thus, on an implementation where INT_MAX is 0x7FFF and UINT_MAX is
> 0xF
--- Comment #3 from joseph at codesourcery dot com 2006-04-18 11:22 ---
Subject: Re: hex and oct constants are converted to
wrong type
On Tue, 18 Apr 2006, rguenth at gcc dot gnu dot org wrote:
> 6.10.1/3
>
> The resulting tokens
> compose the controlling constant expression which i
--- Comment #2 from rguenth at gcc dot gnu dot org 2006-04-18 08:21 ---
6.10.1/3
The resulting tokens
compose the controlling constant expression which is evaluated according to the
rules of
6.6, except that all signed integer types and all unsigned integer types act as
if they have
the
--- Comment #1 from mhx-perl at gmx dot net 2006-04-18 08:17 ---
Created an attachment (id=11291)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11291&action=view)
test code to reproduce the described behaviour
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27195
