> That's a good bit of sleuthing. A couple of questions immediately come to > mind: > Why does gcc and pcc take 4 as their alignment? Why do we take 32? I'm not a guru. But tcc behaviour cost me a day of the problem discovering
> Does this have any performance impact? I don't think so. This alignment is for unusual sections, not for .text .data and so. > Is there a reason you are implementing this with #ifdef? I don't know about gcc defaults on different ARCH > Might we use a preprocessor value (i.e. TCC_DEFAULT_ALIGNMENT) and #define > that in architecture-specific header files instead? May be. But problem exposed only on i386. PS: another problem: 0x1234-123 parsed by tcc as float number by default and there is no switch to dsiable this. And gcc-3.4.6 (4.1.2) understand the above as expression 0x1234 - 123 by default. _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
