search for: ycaan2vyga4yktbx2

On Feb 21, 2010, at 4:10 PM, S3 wrote: > > 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.) This has recently been fixed on trunk. The opt tool no longer adds a default target if a Module has no target attributes, and the optimizers now know

-----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