Hello Henry, I personally vote for a unique binary and multiple 32/64 libs that can generate either 32 or 64 bit using -m32/-m64 flag with -m32 mode be the default. The binary itself can be 32 or 64 bit. (i.e. the 32bit tcc version accepts -m64 as well). The main difficulty I see for the 32bit version is to correctly manage 64bit constants:
#define BIG_INT 0x7ffffffffffffff Which probably requires bignums. Because of this possible constraint, alternate solution is to allow only the tcc 64bit version to generate 64bit mode code when -m64 is supplied (no flag is the same as if -m32 was supplied). By symmetry, le 32bit version of compiler accepts -m32 but refuses -m64 At least with the 64bit compiler, you have a complete toolchain (and one install) for 32/64bit code. Christian -----Original Message----- From: tinycc-devel-bounces+eligis=orange...@nongnu.org [mailto:tinycc-devel-bounces+eligis=orange...@nongnu.org] On Behalf Of Henry Kroll Sent: dimanche 5 décembre 2010 22:08 To: Tinycc-devel@nongnu.org Subject: [Tinycc-devel] Staging for -m32 option I was thinking about adding an -m32 option for the x86_64 config cross. This works, but its rushed and it looks a little bloated. I should probably get some feedback before spending more time on it. http://pastebin.ca/2011419 _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tinycc-devel ---------------------------------------------------------------------------- ----------- Orange vous informe que cet e-mail a ete controle par l'anti-virus mail. Aucun virus connu a ce jour par nos services n'a ete detecte. _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/tinycc-devel
