All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] machine/sh7785lcr: Add new machine for Renesas SH7785 reference board
Date: Sun, 26 Sep 2010 23:11:33 +0200	[thread overview]
Message-ID: <4C9FB705.8040003@eukrea.com> (raw)
In-Reply-To: <AANLkTik=25UpZruyMGJ4LMm6Dd=d6p5yvt4sLcD=EO1k@mail.gmail.com>

Hi,

Le 26/09/2010 22:42, Nobuhiro Iwamatsu a écrit :
> 2010/9/25 Khem Raj<raj.khem@gmail.com>:
>> On Fri, Sep 24, 2010 at 2:56 PM, Nobuhiro Iwamatsu<iwamatsu@nigauri.org>  wrote:
>>> --- a/conf/machine/include/tune-sh4.inc
>>> +++ b/conf/machine/include/tune-sh4.inc
>>> @@ -1,3 +1,5 @@
>>> +# If you want to optimize to sh4a, you need to change
>>> +# from -m4 to m4a.
>>>   TARGET_CC_ARCH = "-ml -m4"
>>>   FEED_ARCH = "sh4"
>>>   BASE_PACKAGE_ARCH = "sh4"
>>
>> you could add another tune file for sh4a called
>> tune-sh4a.inc and include that for appropriate
>> machines. rest of patch looks good to me.
>
> I want to make optimization of m4 a default.
> The reason is because there is not compatibility in m4 and m4a.
> It is a memo for the person whom it wants to optimize in m4a that I
> wrote in tune-sh4.inc.
>
> I thought that I have had better take off a memo if confusion happened
> by this memo.
> How do you think?
>
As Khem said, it's better to have tune-sh4a.inc & tune-sh4.inc in the 
include directory which let the user the possibility to include the one 
he wants in his machine configuration file (without the need to modifiy 
the include file).

Eric



  reply	other threads:[~2010-09-26 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 21:56 [PATCH v2] machine/sh7785lcr: Add new machine for Renesas SH7785 reference board Nobuhiro Iwamatsu
2010-09-24 23:12 ` Khem Raj
2010-09-26 20:42   ` Nobuhiro Iwamatsu
2010-09-26 21:11     ` Eric Bénard [this message]
2010-09-26 22:55       ` Nobuhiro Iwamatsu

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=4C9FB705.8040003@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@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.