Messages in this thread | | | Date | Mon, 9 Jul 2012 15:33:43 +0200 | Subject | Re: [PATCH 00/36] AArch64 Linux kernel port | From | Geert Uytterhoeven <> |
| |
On Mon, Jul 9, 2012 at 4:01 AM, Jon Masters <jonathan@jonmasters.org> wrote: > On 07/08/2012 06:24 PM, Dennis Gilmore wrote: >> I know that the architecture really is new but thats not really clear >> by adding AArch32 into the mix to represent 32 bit arm as ARM has done >> or by calling it armv8. There is enough way to confuse them already why >> confuse things more by adding yet another variable that is AArch64. >> - From my and most of the other Fedora developers that i've discussed it >> with its more like reluctant acceptance of AArch64 than thinking is a >> good idea. > > btw, for clarification of anyone who is confused by the names...the new > architecture is ARMv8. The 64-bit state is AArch64, during which the > processor executes A64 instructions. The 32-bit state is AArch32, during > which the processor executes either A32 ("ARM" version 7+) or T32 > ("Thumb" - I guess Thumb2+ really due to some of deprecation) > instructions. I've noticed that there appears to be a clarification > effort in which AArch64 is used as an architecture name when ARMv8 would > be confusing, which is most of the time if you don't know whether you're > referring to the new A64 instruction set or the older ones.
Ah, A64... sounds better than AArch64... Even AA64 sounds better than AArch64....
> Perhaps this is useful if someone is trying to figure out heads or tails > of the different terms.
Many thanks! I was just googleing what this "T32" thingy was...
Gr{oetje,eeting}s,
Geert
-- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds
| |