search for: in86

On Tue, Aug 19, 2014 at 5:05 PM, Jim Grosbach <grosbach at apple.com> wrote: > Note that it’s not exactly equivalent to enabling -march=core-avx2. It’s > really close, but not 100% the same. What is the difference? and why? It seems really confusing to have this divergence, or to be unable to replicate the *exact* behavior of this (very weird, and IMO *bad* triple) with the standard

Hello, I was looking at sys::getDefaultTargetTriple() (file: lib/Support/Unix/Host.inc ) and there is something unclear to me. std::string sys::getDefaultTargetTriple() { StringRef TargetTripleString(LLVM_DEFAULT_TARGET_TRIPLE); std::pair<StringRef, StringRef> ArchSplit = TargetTripleString.split('-'); // Normalize the arch, since the target triple may not actually

...nce? and why? It seems really confusing to have this divergence, or to be unable to replicate the *exact* behavior of this (very weird, and IMO *bad* triple) with the standard triple of 'x86_64-...' and an '-march' flag. > > It just seems like a reinvention of i386, i486, and iN86, probably for all of the same reasons. If you can encode all the important things in the triple, you can have different library directories for distributions, etc. There’s a few more subtleties, but that’s a reasonable analogy. While the sub-arch is related to a -march= setting, it is very defini...