From: Phil Blundell <pb@pbcl.net>
To: Dragomir Daniel <daniel.dragomir@windriver.com>,
raj.khem@gmail.com, richard.purdie@linuxfoundation.org,
mark.hatle@windriver.com
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] ARMv8-A: Add tune for AArch32 state and AArch64 state
Date: Tue, 29 Mar 2016 18:10:56 +0100 [thread overview]
Message-ID: <1459271456.3476.211.camel@pbcl.net> (raw)
In-Reply-To: <56FAA65F.9060300@windriver.com>
On Tue, 2016-03-29 at 18:59 +0300, Dragomir Daniel wrote:
>
> arch-arm8a.inc add now support for armv8-A processors which support 2
> states:
> 32-bit and 64-bit states. It makes more sense to have support for
> both states
> in the same inc file because both refer to the same arch.
OK. And I assume you feel this is a greater benefit than having the
32-bit ARMv8 bits in a single file that could be shared by ARMv8-R and
ARMv8-M, right?
> So, you say that we should not use aarch32 and aarch64 for armv8a,
> but to use something like armv8a64 and armv8a32?
That would be my preference, but of course it's not my decision to
make.
p.
next prev parent reply other threads:[~2016-03-29 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 15:29 [PATCH] ARMv8-A: Add tune for AArch32 state and AArch64 state Daniel Dragomir
2016-03-28 18:14 ` Otavio Salvador
2016-03-28 22:10 ` Phil Blundell
2016-03-29 15:59 ` Dragomir Daniel
2016-03-29 17:10 ` Phil Blundell [this message]
2016-03-29 18:49 ` Otavio Salvador
2016-03-29 16:07 ` Khem Raj
2016-03-30 16:03 ` Dragomir Daniel
2016-03-30 16:36 ` Khem Raj
2016-03-30 18:10 ` Andre McCurdy
2016-03-30 18:25 ` Khem Raj
2016-03-30 18:53 ` Andre McCurdy
2016-03-30 22:46 ` Phil Blundell
2016-03-30 23:13 ` Khem Raj
2016-03-30 23:59 ` Andre McCurdy
2016-04-01 19:13 ` Otavio Salvador
2016-04-01 22:03 ` Andre McCurdy
2016-04-01 22:13 ` Khem Raj
2016-04-02 11:21 ` Otavio Salvador
2016-03-30 23:11 ` Khem Raj
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=1459271456.3476.211.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=daniel.dragomir@windriver.com \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.