Re: [Tinycc-devel] Can't completely switch C-compiler

[Thomas Preud'homme]

Le mardi 5 février 2013 20:41:59, Robert Clausecker a écrit :
> Hello!
> 
> Today I tried to compile tcc (mob) with the clang compiler. I performed
> the following steps [1] to compile tcc:
> 
>     $ cd src/tinycc
>     $ ./configure --cc=clang --prefix=$HOME
>     $ make
> 
> Now I observe that gcc is still used in some steps:
> 
>         gcc -O2 -m64 -c libtcc1.c -o x86_64/libtcc1.o  -DTCC_TARGET_X86_64
> -Wall -g -O2 gcc -O2 -m64 -c alloca86_64.S -o x86_64/alloca86_64.o 
> -DTCC_TARGET_X86_64 -Wall -g -O2
> 
> What happend here? Why is gcc still used for some compilation steps?

Last time I tried to compile with clang it fails.

> Are the warnings intentional?

You mean, are the warnings false positive or things to worry about? I can't 
tell without seeing the warning you get but at least one of them is legit: 
it's an array member of an union accessed beyond its end. The union is big 
enough anyway but who knows what future optimizations could do.

> 
> Yours, Robert Clausecker

Best regards,

Thomas

> 
> [1]: http://fuz.su/~fuz/tinycc.log
> 
> 
> _______________________________________________
> Tinycc-devel mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/tinycc-devel

signature.asc
Description: This is a digitally signed message part.