Hi,
On Sun, 27 May 2012, Rick Hodgin wrote:
Didier,
You're able to take the code and modify that requirement. It seems
straight-forward enough that TinyCC is (in memory at compile-time)
determining the target size, regardless of the storage size, and using
that for the storage size in memory. You could alter that code to
always use the smallest storage-size, and automatically upsize to the
larger form, such as something stored as 1..7 bits always being stored
as a single byte, even if it's scoped as an int.
If one changes anything at all then it only makes sense to change it so as
to be layout compatible with GCC. A third layout (GCC, TCC-old, TCC-new)
wouldn't help. Although the rules of GCC are relatively obscure and
complex in corner cases.
Ciao,
Michael.
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
