| |||||||||||||
Haley: We're doing an ARM64 OpenJDK port!Haley: We're doing an ARM64 OpenJDK port!Posted Oct 26, 2012 19:20 UTC (Fri) by butlerm (subscriber, #13312)In reply to: Haley: We're doing an ARM64 OpenJDK port! by aryonoco Parent article: Haley: We're doing an ARM64 OpenJDK port!
> And it's actually technically called AArch64
Marketing fail.
(Log in to post comments)
Haley: We're doing an ARM64 OpenJDK port! Posted Oct 27, 2012 0:48 UTC (Sat) by cesarb (subscriber, #6266) [Link]
ARM is as bad at that as Sun. The ARM11, which is an ARMv6, is older than the A5, which is an ARMv7. If you compile something for ARMv7 or later, it will not run on an ARM11. And do not confuse ARMv7 with ARM7 - the later is an ARMv3, or later an ARMv4 or ARMv5.
The ARMv7 family has the A5, A7, A8, A9, and A15. Let's hope it does not get near A32, else things will get even more confusing.
Haley: We're doing an ARM64 OpenJDK port! Posted Oct 31, 2012 2:02 UTC (Wed) by wookey (subscriber, #5501) [Link]
Debian and Ubuntu are calling the arch 'arm64'. The upstream GNU triplet remains 'aarch64-linux-gnu'.
If you really care there is a doc somewhere carefully distinguishing the names of the architecture, 64-bit instruction set, 32-bit instruction set, etc. But I reckon most people without marketing droids standing behind them will just call it arm64 (or armv8).
I've been having fun with bootstrapping: http://wiki.debian.org/Arm64Port
You can install a quantal amd64 chroot with cross toolchain and start building stuff.
Linaro have OE image builds that can be run on ARM's free-beer 'Fast' Model (which is not at all fast) http://www.linaro.org/engineering/armv8
|
|||||||||||||