Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune-cortexa72-cortexa53: Add tune
Date: Sat, 14 Dec 2019 03:22:49 +0200	[thread overview]
Message-ID: <20191214012249.GC8776@localhost> (raw)
In-Reply-To: <CAJdd5GY4Ld9t1fo1sC2mK7nXuBCi=T39DwstZ5ZnTNFrEp226A@mail.gmail.com>

On Fri, Dec 13, 2019 at 06:47:33PM -0600, Joshua Watt wrote:
> On Fri, Dec 13, 2019 at 5:10 PM Adrian Bunk <bunk@stusta.de> wrote:
> >
> > On Fri, Dec 13, 2019 at 04:03:09PM -0600, Joshua Watt wrote:
> > > Adds a tune for Cortex-A72 Cortex-A53 big.LITTLE SoCs, e.g.  Rockchip
> > > RK3399
> > >...
> > > +TUNE_FEATURES_tune-cortexa72-cortexa53 = "${TUNE_FEATURES_tune-aarch64} cortexa72-cortexa53"
> > >...
> >
> > Looking at the gcc sources cortexa72-cortexa53 defaults to crc enabled,
> > so TUNE_FEATURES_tune-cortexa72-cortexa53 must contain crc.
> 
> I think that's armv8.1-a, the cortex A72 is only armv8-a (at least
> AFAICT), so I think crc would still be an optional feature.
>...

It is optional for armv8-a, but not for Cortex A53 or A72.

What matters in practice is that gcc automatically enables it for 
cortex-a72.cortex-a53, so the resulting code might not run on
armv8-a hardware without support for crc - things will break
if the tune features are not 100% aligned with whatever gcc
is doing.

cu
Adrian


  reply	other threads:[~2019-12-14  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-13 22:03 [PATCH] tune-cortexa72-cortexa53: Add tune Joshua Watt
2019-12-13 22:05 ` Mark Hatle
2019-12-13 22:08   ` Joshua Watt
2019-12-13 23:10 ` Adrian Bunk
2019-12-14  0:47   ` Joshua Watt
2019-12-14  1:22     ` Adrian Bunk [this message]
2019-12-14  1:28       ` Joshua Watt
2019-12-14  1:41         ` Adrian Bunk
2019-12-14  1:48           ` Joshua Watt
2019-12-14  0:54 ` [PATCH v2] tune-cortexa72-cortexa53: Add tunes Joshua Watt
2019-12-14  1:21   ` Andre McCurdy
2019-12-14  1:29     ` Joshua Watt
2019-12-14 16:06   ` [PATCH v3] " Joshua Watt

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=20191214012249.GC8776@localhost \
    --to=bunk@stusta.de \
    --cc=jpewhacker@gmail.com \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox