tinycc-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Tinycc-devel] _Generic or __builtin_choose_expr


From: uso ewin
Subject: Re: [Tinycc-devel] _Generic or __builtin_choose_expr
Date: Thu, 6 Jul 2017 14:24:47 +0200

On Thu, Jul 6, 2017 at 2:09 PM, uso ewin <address@hidden> wrote:
> On Thu, Jul 6, 2017 at 6:11 AM, Christian Jullien <address@hidden> wrote:
>> On Windows 32bit as with RPi I get:
>> Test: 94_generic...
>> --- ../../tests/tests2/94_generic.expect        2017-07-06
>> 06:06:36.520552800 +0200
>> +++ 94_generic.output   2017-07-06 06:07:53.359318000 +0200
>> @@ -1,9 +1 @@
>> -20
>> -20
>> -123
>> -2
>> -5
>> -1
>> -2
>> -3
>> -1
>> +94_generic.c:44: error: type march twice
>> make[2]: *** [Makefile:49: 94_generic.test] Error 1
>>
>
> Ok the error happen because parse_btype, does never return VT_LONG.
> So I guess if a _Generic expression contain a long long and a long in
> 64bit the error would happen too.
>
> I guess a solution would be either a global variable to force
> parse_btype to let long as long, or to patch every functions that call
> parse_btype so it take another argument which is here to force
> parse_btype to keep long as long.
>
> sorry for adding a bug.
>
> Matthias

I've push the fix on my mob:
https://github.com/cosmo-ray/tcc/commit/fb26db96828291a9c4ae94394f1aa4d1289ae14f

I've add a small commit so generic unqualify volatile too:
https://github.com/cosmo-ray/tcc/commit/e87939bfd385f412375f8a599e0b32914b5e8488

If your okay with that, I push it on mob.

Matthias



reply via email to

[Prev in Thread] Current Thread [Next in Thread]