Displaying 4 results from an estimated 4 matches for "v6hl".
Did you mean:
26hl
2016 Jan 08
2
Diff to add ARMv6L to Target parser
...rser.cpp (revision 257090)
+++ lib/Support/TargetParser.cpp (working copy)
@@ -401,6 +401,7 @@
.Case("v5", "v5t")
.Case("v5e", "v5te")
.Case("v6j", "v6")
+ .Case("v6l", "v6")
.Case("v6hl", "v6k")
.Cases("v6m", "v6sm", "v6s-m", "v6-m")
.Cases("v6z", "v6zk", "v6kz")
Index: unittests/ADT/TripleTest.cpp
===================================================================
--- unittests/ADT/...
2016 Jan 04
2
Diff to add ARMv6L to Target parser
....
>
> ARMv6l was definitely there once. I'm not sure what happened.
>
> I'm copying the ARM folks that did most of the recent changes in hope they can
> shed some light.
Going back through SVN history, I cannot find any evidence that ARMv6L ever existed.
There used to be ARMv6HL, until r252903 changed it from an architecture variant into an alias for ARMv6K; i.e. ARMv6HL can still be used in a target triple.
For a reference, http://llvm.org/viewvc/llvm-project/llvm/trunk/lib/Support/TargetParser.cpp?revision=238651 is the last version of TargetParser before any of our cha...
2016 Jan 03
2
Diff to add ARMv6L to Target parser
Hi all.
I’ve been working with Swift on ARMv6 and v7. While working with ARMv6 on linux, I noticed that my arm architecture canonicalization code didn’t produce the expected result. The code that I had been using (within Swift’s Driver.cpp the following:
static llvm::Triple computeTargetTriple(StringRef DefaultTargetTriple) {
llvm::Triple triple = llvm::Triple(DefaultTargetTriple);
//
2016 Jan 05
6
Diff to add ARMv6L to Target parser
> 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