From: Tom Rini <tom_rini@mentor.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] gcc: Add ability for tune files to pass in configure options to gcc
Date: Mon, 1 Aug 2011 09:44:48 -0700 [thread overview]
Message-ID: <4E36D800.1050906@mentor.com> (raw)
In-Reply-To: <1312214835.30326.528.camel@phil-desktop>
On 08/01/2011 09:07 AM, Phil Blundell wrote:
> On Mon, 2011-08-01 at 09:37 -0500, Kumar Gala wrote:
>> Not sure I understand the statement about disambiguate the resulting compilers, on PPC where I intend to utilize this we'd have the toolchains already named something like:
>
> The thing about disambiguating was that, if you're going to modify the
> configure opts for gcc-cross based (indirectly) on ${MACHINE} you need
> to consider what happens if you have a single build directory that's
> being used for multiple MACHINEs.
What, I think, Kumar is driving at is why are you saying MACHINE when
it's a per core tune he's doing. eg, every e5500 would do --with-cpu=e5500
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-08-01 16:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 14:21 [PATCH] gcc: Add ability for tune files to pass in configure options to gcc Kumar Gala
2011-08-01 14:30 ` Phil Blundell
2011-08-01 14:37 ` Kumar Gala
2011-08-01 16:07 ` Phil Blundell
2011-08-01 16:44 ` Tom Rini [this message]
2011-08-01 16:57 ` Richard Purdie
2011-08-02 13:11 ` Kumar Gala
2011-08-02 13:42 ` Richard Purdie
2011-08-08 16:32 ` Kumar Gala
2011-08-08 23:22 ` Richard Purdie
2011-08-08 16:35 ` Kumar Gala
2011-08-08 19:33 ` Richard Purdie
2011-08-02 13:02 ` Phil Blundell
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=4E36D800.1050906@mentor.com \
--to=tom_rini@mentor.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.