tinycc-devel
[Top][All Lists]
Advanced

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

[Tinycc-devel] ?????? ?????? bug


From: lrt
Subject: [Tinycc-devel] ?????? ?????? bug
Date: Thu, 9 Jun 2022 20:04:16 +0800

Hi,

I tested vs, it's same.
It's not bug.

Thks!

------------------ ???????? ------------------
??????: "tinycc-devel" <ml@vr5.epicgamer.org>;
????????: 2022??6??9??(??????) ????0:48
??????: "tinycc-devel"<tinycc-devel@nongnu.org>;
????: Re: [Tinycc-devel] ?????? bug

Hello,

On 6/8/22 6:26 PM, Brian Callahan wrote:
> On 6/8/2022 11:12 AM, lrt wrote:
>> int main(int argc, char **argv)
>> {
>> printf("Hello!\n");
>> //uint64_t n = 0xffffffff;
>> //printf("%lld\n", n);
>> printf("%lld\n", 0xffff);
>> printf("%llu\n", 0xffff);
>> return 0;
>> }
>> output:
>> Hello!
>> 247414872441159679
>> 247414872441159679
>>
>> Remove comments??different result.
> You were already told once by Kyryl to update your TCC version or let us
> know what platform and TCC version you're using. You still haven't done
> either. It is impossible to help you without more information, though
> Kyryl's suggestion of update your version of TCC is almost certainly the
> correct one. (Alternatively, did you write your own libc and get printf
> format string handling totally wrong?)
>
> It would be near unbelievable if TCC couldn't correctly handle such a
> simple program. But of course, it does.

It's the same problem as in previous test case - format
is for long long but the value passed is long.

So it's not a problem with tcc.

BTW, 247414872441159679 = 0x36efe840000ffff


Vad

_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

reply via email to

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