search for: llcs

...0 and z196, since there were significant additions to the architecture in z196. Until now we've been getting that by implicitly using -mcpu=z10 for cross testing on the usual x86_64 buildbots and implicitly using -mcpu=native (-mcpu=z196) on the z buildbot. We could do it instead by having two llcs and FileChecks per CodeGen/SystemZ test, which would give better cross-toolchain coverage, but would almost double the test time. Would that still be OK? Thanks, Richard

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