public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@kernel.crashing.org>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Updates for ARM tunings
Date: Wed, 31 Jan 2024 17:29:39 -0600	[thread overview]
Message-ID: <1706743783-10659-1-git-send-email-mark.hatle@kernel.crashing.org> (raw)

From: Mark Hatle <mark.hatle@amd.com>

cortexa78 missing seems to be an oversight.  It (according to wikipedia) is a
successor to the cortexa77 which already exists.  This was created by
copying the cortexa77 and changing it to be a78.  A test system was build to
verify no obvious issues with the toolchain.

The remaining three changes are related.  I've got a need for a cortex-r5 and
cortex-r52 that enables the hard-float calling convention (this might also
be useful to others with other cortex-r and maybe even cortex-m processors,
but I'm not in a position to know this outside of my specific need.)

tune-cortexr5 simply adds an hf variant that adds the callconvention-hard.
Since there is no armv7r-vfp3d16 w/ this, the package_arch list is more
limited then the regular r5.

tune-cortexr52 requires the change to feature-arm-vfp to allow the setting
when 'simd' is enabled (since we don't specify vfp or neon).  Otherwise
this follows the same convention as the r5 change.

Mark Hatle (4):
  tune-cortexa78.inc: Add cortexa78 tune, based on cortexa77
  feature-arm-vfp.inc: Allow hard-float on newer simd targets
  tune-cortexr5: Add hard-float variant
  tune-cortexr52: Add hard-float variant

 .../machine/include/arm/armv7r/tune-cortexr5.inc |  5 +++++
 .../include/arm/armv8-2a/tune-cortexa78.inc      | 16 ++++++++++++++++
 .../include/arm/armv8r/tune-cortexr52.inc        |  5 +++++
 .../conf/machine/include/arm/feature-arm-vfp.inc |  3 ++-
 4 files changed, 28 insertions(+), 1 deletion(-)
 create mode 100644 meta/conf/machine/include/arm/armv8-2a/tune-cortexa78.inc

-- 
2.34.1



             reply	other threads:[~2024-01-31 23:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 23:29 Mark Hatle [this message]
2024-01-31 23:29 ` [PATCH 1/4] tune-cortexa78.inc: Add cortexa78 tune, based on cortexa77 Mark Hatle
2024-02-01  2:09   ` [OE-core] " Khem Raj
2024-02-01  2:15     ` Mark Hatle
2024-01-31 23:29 ` [PATCH 2/4] feature-arm-vfp.inc: Allow hard-float on newer simd targets Mark Hatle
2024-01-31 23:29 ` [PATCH 3/4] tune-cortexr5: Add hard-float variant Mark Hatle
2024-01-31 23:29 ` [PATCH 4/4] tune-cortexr52: " Mark Hatle

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=1706743783-10659-1-git-send-email-mark.hatle@kernel.crashing.org \
    --to=mark.hatle@kernel.crashing.org \
    --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