[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] State of the tcc project (jiang)
From: |
Aidan Dodds |
Subject: |
Re: [Tinycc-devel] State of the tcc project (jiang) |
Date: |
Fri, 20 Jun 2014 11:20:13 +0100 |
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 |
I see now that must be intentional, but that's also very dangerous.
It looks like you are trying to reproduce a gcc bug, why not make that
optional? Perhaps proposing a compatibility mode if it would be a useful
thing to have.
Even if its sensible, you should really control what garbage data you
are throwing out from that format specifier. Why not generate a random
value to Emmit? That would seem safer for a large number of reasons.
I should point out I don't know what problem you are trying to solve,
this just strikes me as very dodgy code, especially when it seems you are
purposefully break working code, to implement a bug. That surely
effects everyone using tcc.
On 20/06/2014 11:08, Aidan Dodds wrote:
On 20/06/2014 06:58, jiang wrote:
printf("%d %d %d %d %d\n",
+ st1.f2, st1.f3, st1.f4, st1.f5);
Am i being stupid, or do you specify 5 format specifiers with only 4
arguments?!
_______________________________________________
Tinycc-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/tinycc-devel