[LLVMdev] Proposal: Move host CPU auto-detection out of the TargetMachine

[Eric Christopher]

I'm not a huge fan of this because then you get to decide on a default
for all the ports, but I can understand if people want to move this
way to reduce uncertainty.

Alternately have a way for the backend to pretty print out the results
of the auto-detection when asked?

*shrug*

-eric

On Tue, Apr 8, 2014 at 1:59 AM, Jim Grosbach <grosbach at apple.com> wrote:
> All,
>
> Currently the X86 backend does CPU auto-detection and subtarget feature detection when the TargetMachine is created if no explicit CPU was specified. It's counterintuitive for low level tools like 'llc' to do this, as it means the same .ll file compiled on heterogenous machines generates different results from the same 'llc' command line. It is still useful to be able to opt-in to such behavior to, for example, replicate clang's behavior when -mcpu=native is supplied to clang. My thought is to do something similar here and teach 'llc' to recognize -mcpu=native and probe the host CPU if that is given. The subtarget features will then be filled in according to the feature string for that CPU. This (a) changes the auto-detection from opt-out to opt-in and (b) moves the logic out of the core target backend and into the tools drivers.
>
> Attached are draft patches that do this for X86. Similar but smaller cleanups can also be done for SystemZ and PowerPC if it's agreed this is a good idea.
>
> -Jim
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>