[LLVMdev] Default target

S3 scubed at nostratic.lingcog.iit.edu
Sun Feb 21 16:10:32 PST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Currently, if you have BitCode that does not
specify a target, it gets a default architecture.
This is especially odd if you are doing
llvm-ld -native
but it first applies optimizations for
a target other than what it is currently compiling for.

Ideally, target-specific optimizations wouldn't be
applied until a target was given.
This would allow simple programs to be target-agnostic.
(And therefore more likely to work for newcomers.)

Why is there a default target?
Why can't those optimizations just be skipped until there is one?
(To be clear: I am assuming there is a reason for this.
I am asking what it is.)

Especially in the case of llvm-ld -native,
why doesn't it set the target to the platform
it is compiling for?
Failing that, it could use the platform it is
currently running on as the target.

- --
main(){char s[]="+~{Y$-:>2vp5z^",c=244,i;int j=44404;
for(;j>0;j--)for(i=0;i<14;i++)c+=s[i]-=c;puts(s);}
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkuBy3gACgkQxzVgPqtIcftJ1wCfUen0P0Hqe+I/4gzqQvh0lLO8
HAAAn2BInGLdEUmX5Px2+3KRgAVEGtBS
=Es2n
-----END PGP SIGNATURE-----



More information about the llvm-dev mailing list