Displaying 3 results from an estimated 3 matches for "armv7b".
Did you mean:
armv7
2016 Jan 05
2
Diff to add ARMv6L to Target parser
...has semantic
>> meaning, but I suppose I could live with it.
>
> Not really.
I disagree. "armv7l" is created specifically by Linux appending a
little-endian 'l' to an "armv7" base. It's much less common (because
no-one cares about big-endian), but "armv7b" also exists. As do
"armv6l", "armv6b" and probably "armv8" equivalents too if you ran a
32-bit kernel there. Adding random aliasing on an ad-hoc basis doesn't
scale or represent what's really going on.
> In the Arch side, ARMv7l is *really* ARMv7A, so...
2016 Jan 05
2
Diff to add ARMv6L to Target parser
On 5 January 2016 at 09:13, Renato Golin <renato.golin at linaro.org> wrote:
> Anyhow, Artyom's proposal is the best, IMO, to treat it like an alias
> and handle like v7A internally. If we end up needing specific
> decisions in the driver, it should stay in the driver.
That's rather a hack, given that the 'l' actually has semantic
meaning, but I suppose I could live
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 Linux kernel will present itself as via "uname
-a" which, as James said, is a vaguely sane way to seed a triple.
> The ARM documents define a list of o...