Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] Make ppce300c3 tune hard-float by default
Date: Tue, 01 Apr 2014 11:48:03 +0100	[thread overview]
Message-ID: <1396349283.1432.1.camel@ted> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B3AA247@post.tritech.se>

On Tue, 2014-04-01 at 07:54 +0000, Mats Kärrman wrote:
> Hi Khem,
> 
> Thanks for your feedback!
> 
> On Tuesday, April 01, 2014 7:37 AM, Khem Raj wrote:
> > On Fri, Mar 28, 2014 at 9:43 AM, Mats Kärrman <Mats.Karrman@tritech.se> wrote:
> >> +# glibc configure options to make use of 603e specific sqrt/sqrtf routines
> >> +GLIBC_EXTRA_OECONF += "${@bb.utils.contains("TUNE_FEATURES", "ppce300c3", "--with-cpu=e300c3", "", d)}"
> >
> > looks good, may be the comment above can be more explanatory saying that
> > glibc aliases e300c3 sqrt/sqrtf to 600e versions
> 
> The above statement depends on an added "Implies" file in eglibc and,
> more important on a previous patch adding support for 603e/fpu sqrt.
> 
> How is the new Implies file best added, as a patch to the previous patch
> or as a new patch?

Since this hasn't merge yet please send another patch. If it had merged,
an incremental one would be needed.

Cheers,

Richard



  reply	other threads:[~2014-04-01 10:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 16:43 [RFC PATCH] Make ppce300c3 tune hard-float by default Mats Kärrman
2014-04-01  5:37 ` Khem Raj
2014-04-01  7:54   ` Mats Kärrman
2014-04-01 10:48     ` Richard Purdie [this message]
2014-04-01 11:44       ` Mats Kärrman
2014-04-01 12:02         ` Richard Purdie

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=1396349283.1432.1.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Mats.Karrman@tritech.se \
    --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