From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] tune-ppce500: correct the -mfloat-gprs compiler option
Date: Fri, 30 Mar 2012 17:57:32 -0500 [thread overview]
Message-ID: <4F763A5C.5030900@windriver.com> (raw)
In-Reply-To: <1333147814-4990-1-git-send-email-kergoth@gmail.com>
I noticed the same problem in the tuning rework that I've gone pending. I'm
currently working on validating it and hope to have something for merging once I
get done validating all 120 tunes.
--Mark
On 3/30/12 5:50 PM, Christopher Larson wrote:
> From: Christopher Larson<chris_larson@mentor.com>
>
> Per Edmar at Freescale, e500v2 needs -mfloat-gprs=double, but e500v1 needs
> -mfloat-gprs=single.
>
> Signed-off-by: Christopher Larson<chris_larson@mentor.com>
> ---
> meta/conf/machine/include/tune-ppce500.inc | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/conf/machine/include/tune-ppce500.inc b/meta/conf/machine/include/tune-ppce500.inc
> index feb1967..c966560 100644
> --- a/meta/conf/machine/include/tune-ppce500.inc
> +++ b/meta/conf/machine/include/tune-ppce500.inc
> @@ -7,7 +7,7 @@ TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "ppce500", "-mcpu=8540", "
> TUNE_PKGARCH_tune-ppce500 = "ppce500"
>
> TUNEVALID[spe] = "Enable SPE ABI extensions"
> -TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "spe", "-mabi=spe -mspe -mfloat-gprs=double", "", d)}"
> +TUNE_CCARGS += "${@bb.utils.contains("TUNE_FEATURES", "spe", "-mabi=spe -mspe -mfloat-gprs=single", "", d)}"
>
> TARGET_FPU = "ppc-efs"
>
prev parent reply other threads:[~2012-03-30 23:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 22:50 [PATCH] tune-ppce500: correct the -mfloat-gprs compiler option Christopher Larson
2012-03-30 22:57 ` Mark Hatle [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=4F763A5C.5030900@windriver.com \
--to=mark.hatle@windriver.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