From: Khem Raj <raj.khem@gmail.com>
To: chunrong.guo@nxp.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] tune-ppce500v1: Add a tune file for PowerPC e500v1 cores
Date: Thu, 14 Jun 2018 09:36:16 -0700 [thread overview]
Message-ID: <cfb8f094-4f7a-5816-113d-1014d4180649@gmail.com> (raw)
In-Reply-To: <1528968301-3209-1-git-send-email-chunrong.guo@nxp.com>
[-- Attachment #1.1: Type: text/plain, Size: 1896 bytes --]
Hi Chunrong
On 6/14/18 2:25 AM, chunrong.guo@nxp.com wrote:
> From: Chunrong Guo <chunrong.guo@nxp.com>
>
> Signed-off-by: Chunrong Guo <chunrong.guo@nxp.com>
> ---
> meta/conf/machine/include/tune-ppce500v1.inc | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
> create mode 100644 meta/conf/machine/include/tune-ppce500v1.inc
>
> diff --git a/meta/conf/machine/include/tune-ppce500v1.inc b/meta/conf/machine/include/tune-ppce500v1.inc
> new file mode 100644
> index 0000000..509c81b
> --- /dev/null
> +++ b/meta/conf/machine/include/tune-ppce500v1.inc
> @@ -0,0 +1,20 @@
> +DEFAULTTUNE ?= "ppce500v1"
> +
> +require conf/machine/include/powerpc/arch-powerpc.inc
> +
> +TUNEVALID[ppce500v1] = "Enable ppce500v1 specific processor optimizations"
> +TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'ppce500v1', ' -mcpu=8540', '', d)}"
> +
> +TUNEVALID[spe] = "Enable SPE ABI extensions"
> +TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', [ 'ppce500v1', 'spe' ], ' -mabi=spe -mspe -mfloat-gprs=double', '', d)}"
> +TARGET_FPU .= "${@bb.utils.contains('TUNE_FEATURES', [ 'ppce500v1' , 'spe' ], 'ppc-efd', '', d)}"
> +
> +# spe is defined potentially in two places, so we want to be sure it will
> +# only write spe once to the ABIEXTENSIONS field.
> +SPEABIEXTENSION = "${@bb.utils.filter('TUNE_FEATURES', 'spe', d)}"
> +ABIEXTENSION .= "${SPEABIEXTENSION}"
> +
> +AVAILTUNES += "ppce500v1"
> +TUNE_FEATURES_tune-ppce500v1 = "m32 spe ppce500v1"
> +TUNE_PKGARCH_tune-ppce500v1 = "ppce500v1"
> +PACKAGE_EXTRA_ARCHS_tune-ppce500v1 = "ppce500v1"
>
I must inform that spe backend is moved into obsoleted backends in gcc
and is slated to be gone in gcc9 unless someone shows up to maintain it.
With that in mind, I think we should wait and not add this to oe-core
since this will also become obsolete as we move to new compiler.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 201 bytes --]
prev parent reply other threads:[~2018-06-14 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 9:25 [PATCH] tune-ppce500v1: Add a tune file for PowerPC e500v1 cores chunrong.guo
2018-06-14 16:36 ` 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=cfb8f094-4f7a-5816-113d-1014d4180649@gmail.com \
--to=raj.khem@gmail.com \
--cc=chunrong.guo@nxp.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 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.