search for: v6a

...) <https://github.com/apple/swift-llvm/blob/stable/lib/Support/TargetParser.cpp#L387> that matches the trailing ‘l’ (or ‘b’) and treats it the same way that ‘el’ and ‘eb’ are now? This function would return v7 or v6 in the case of armv7l or armv6l, respectively (or, if it’s preferred, v7a or v6a). It seems like this is closer to the “correct” approach. It does show potentially inappropriate deference to Linux’s choice in the matter, but at least it’s not making sub-architectures that don’t exist. Thoughts? - Will > On Jan 5, 2016, at 4:48 AM, Renato Golin via llvm-dev <llvm-dev a...

Hello! Trying to compile, build, install and run Opus. My config: Ubuntu console (Windows 10 app). First problem, configure says openssl is missing. My system says that i have openssl already. Which openssl does it need? Using aptitude, i've installed everything with openssl name in it. That's tons of files and gigabytes of data. But it worked somehow. Second problem, flac-1.3.2 -

...hat if I add logic to >> llvm::ARM::getCanonicalArchName() that matches the trailing ‘l’ (or ‘b’) and >> treats it the same way that ‘el’ and ‘eb’ are now? This function would >> return v7 or v6 in the case of armv7l or armv6l, respectively (or, if it’s >> preferred, v7a or v6a). It seems like this is closer to the “correct” >> approach. It does show potentially inappropriate deference to Linux’s >> choice in the matter, but at least it’s not making sub-architectures that >> don’t exist. > > This is the final "better" solution, but it...

> You assume triples make sense. That's the first mistake everyone does > when thinking about triples. :) I know they don't make sense in many corner cases, but I think discarding logic where it *does* exist is a mistake. > AFAIK, "ARMv7B" is only used by HighBank, which is no more. But that, > too, was "ARMv7A big endian". I believe it's what any