From: Khem Raj <raj.khem@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc-configure-common.inc: duplicate armv7a over-ride for armv8a
Date: Thu, 24 Mar 2016 16:58:42 -0700 [thread overview]
Message-ID: <CCAE827A-00BF-409A-9EB5-B728192D89CB@gmail.com> (raw)
In-Reply-To: <1458861705.2038.43.camel@pbcl.net>
[-- Attachment #1.1: Type: text/plain, Size: 1424 bytes --]
> On Mar 24, 2016, at 4:21 PM, Phil Blundell <pb@pbcl.net> wrote:
>
> On Thu, 2016-03-24 at 15:22 -0700, Khem Raj wrote:
>>
>> > On Mar 24, 2016, at 11:32 AM, Phil Blundell <pb@pbcl.net <mailto:pb@pbcl.net>> 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.
[-- Attachment #1.2: Type: text/html, Size: 6965 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 211 bytes --]
prev parent reply other threads:[~2016-03-24 23:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 3:19 [PATCH] gcc-configure-common.inc: duplicate armv7a over-ride for armv8a Andre McCurdy
2016-03-24 4:19 ` Khem Raj
2016-03-24 5:16 ` Andre McCurdy
2016-03-24 8:03 ` Khem Raj
2016-03-24 17:37 ` Andre McCurdy
2016-03-24 18:32 ` Phil Blundell
2016-03-24 21:41 ` Richard Purdie
2016-03-24 22:28 ` Khem Raj
2016-03-24 22:22 ` Khem Raj
2016-03-24 23:21 ` Phil Blundell
2016-03-24 23:58 ` Khem Raj [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CCAE827A-00BF-409A-9EB5-B728192D89CB@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox