I tested vs, it's same.
It's not bug.
------------------ ???????? ------------------
??????: "tinycc-devel" <firstname.lastname@example.org>;
????????: 2022??6??9??(??????) ????0:48
????: Re: [Tinycc-devel] ?????? bug
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)
>> //uint64_t n = 0xffffffff;
>> //printf("%lld\n", n);
>> printf("%lld\n", 0xffff);
>> printf("%llu\n", 0xffff);
>> return 0;
>> 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
Tinycc-devel mailing list