> -----Original Message----- > From: Adrian Bunk <[email protected]> > Sent: den 3 mars 2020 14:40 > To: Peter Kjellerstedt <[email protected]> > Cc: Junling Zheng <[email protected]>; Khem Raj > <[email protected]>; [email protected]; > [email protected] > Subject: Re: [OE-core] [PATCH] arch-arm64.inc: Do not append aarch64 in > MACHINEOVERRIDES > > On Tue, Mar 03, 2020 at 11:59:58AM +0000, Peter Kjellerstedt wrote: > >... > > Which corresponds to how it is done for armv7*. > > > > At least we currently rely on being able to do, e.g.: > > > > COMPATIBLE_MACHINE = "aarch64|armv7a|armv7ve" > > > > and if you remove "aarch64" from MACHINEOVERRIDES, we need a suitable > > substitute. > > What does "aarch64" actually mean here? > Does it also cover 32bit-only aarch64 CPUs?
We haven't had to reflect about that as all aarch64 based SoCs we use are 64-bit only. So I guess we live in a simplified world. Still, we need a way to separate them from our armv7 or mips based SoCs... > Similar to x86 there are 3 ABIs, and aarch64ilp32 is different from > aarch32. > > Different from x86, there is no ABI that is available in all aarch64 CPUs. > They can be 32bit-only or 64bit-only, and aarch32 support is optional. > > > //Peter > > cu > Adrian //Peter -- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
