On 2 April 2013 16:17, Lluís Batlle i Rossell <vi...@viric.name> wrote: > On Tue, Apr 02, 2013 at 03:29:29PM +0200, grischka wrote: >> Rob wrote: >> >Anyways, perhaps there should be a -fcommon flag on tcc, just like >> >gcc/clang. >> >> -f[no]-common already exists in tcc. It sets TCCState->nocommon. >> >> The default for s->nocommon once was 0 (meaning common=yes, as in gcc) >> but I changed it to 1 (libtcc.c:1016) eventually because of problems >> in some test program. I didn't investigate further what the problem >> was though. But it probably is a problem in tcc (with using common=yes) >> because there was no problem when using gcc to compile/link that program.
Ah right, fair enough. > As an additional point, if "int a;" is in multiple translation units, > I think that tcc reports a linking error, but links nevertheless. This is > also a > bit strange behaviour, no? I get this too,and the resulting binary segfaulted for me. Not sure what's causing it. Rob _______________________________________________ Tinycc-devel mailing list Tinycc-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/tinycc-devel
