> On Mar 24, 2016, at 4:21 PM, Phil Blundell <[email protected]> wrote: > > On Thu, 2016-03-24 at 15:22 -0700, Khem Raj wrote: >> >> > On Mar 24, 2016, at 11:32 AM, Phil Blundell <[email protected] >> > <mailto:[email protected]>> wrote: >> > >> > On Thu, 2016-03-24 at 10:37 -0700, Andre McCurdy wrote: >> >> >> >> Renaming armv8a -> aarch32 is going to affect almost every line in >> >> the patch. We should probably drop the current patch from master- >> >> next. >> > >> > "AArch32" applies retrospectively to all older versions of the ARM >> > architecture as well, >> >> not really. Arm refers to aarch32 specifically when we use 32-bit on ARMv8 >> so atleast we are speaking same terms. > > See the glossary at: > > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.aeg0014g/ABCDEFGH.html > > <http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.aeg0014g/ABCDEFGH.html> > > AArch32 state > The ARM 32-bit Execution state that uses 32-bit general purpose registers, > and a 32-bit program counter (PC), stack pointer (SP), and link register > (LR). AArch32 Execution state provides a choice of two instruction sets, A32 > and T32. > > In implementations of versions of the ARM architecture before ARMv8, and in > the ARM R and M architecture profiles, execution is always in AArch32 state.
I am not saying its any different technically. But aarch32 as term is only used w.r.t. armv8 > > p.
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
