From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] add Kconfig option for optimizing for cell
Date: Fri, 14 Sep 2007 18:36:21 -0500 [thread overview]
Message-ID: <1189812981.24878.6.camel@localhost.localdomain> (raw)
In-Reply-To: <200709150302.23743.arnd@arndb.de>
On Sat, 2007-09-15 at 03:02 +0200, Arnd Bergmann wrote:
> On Saturday 15 September 2007, Josh Boyer wrote:
> > On Sat, 2007-09-15 at 02:21 +0200, Arnd Bergmann wrote:
> > > Since the PPE on cell is an in-order core, it suffers significantly
> > > from wrong instruction scheduling. This adds an Kconfig option that
> > > enables passing -mtune=cell to gcc in order to generate object
> > > code that runs well on cell.
> >
> > Which version of gcc supports that?
> >
>
> gcc-4.3 will be the first official release that has everything in it,
> and I think 4.1 has some parts. However, there are many patched gcc
> versions in various distributions, so I tried to avoid being too
> specific about the version here.
>
> Of course, on gcc versions that don't support -mtune=cell, the
> Kconfig option does not make a difference.
Sure. I was just wondering if mentioning the first official GCC version
in the Kconfig description would help prevent users from selecting the
option for GCCs that don't support it and then being confused later when
nothing happens. Your call though.
josh
next prev parent reply other threads:[~2007-09-15 1:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 0:21 [PATCH] add Kconfig option for optimizing for cell Arnd Bergmann
2007-09-14 23:07 ` Josh Boyer
2007-09-15 1:02 ` Arnd Bergmann
2007-09-14 23:36 ` Josh Boyer [this message]
2007-09-15 0:50 ` Segher Boessenkool
2007-09-15 1:02 ` Arnd Bergmann
2007-09-15 13:13 ` David Woodhouse
2007-09-15 13:30 ` Arnd Bergmann
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=1189812981.24878.6.camel@localhost.localdomain \
--to=jwboyer@linux.vnet.ibm.com \
--cc=arnd@arndb.de \
--cc=linuxppc-dev@ozlabs.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