linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, cbe-oss-dev@ozlabs.org
Subject: Re: [Cbe-oss-dev] [RFC, PATCH] selection of CPU optimization
Date: Thu, 12 Apr 2007 21:50:04 +0200	[thread overview]
Message-ID: <e5b10849669a764f002d1926838edc76@kernel.crashing.org> (raw)
In-Reply-To: <200704121926.03723.arnd@arndb.de>

>> I think -mcpu=8540 will work for e500 (same for tune)
>
> Interestingly, -mcpu=8540 is known to gcc, according to
> gcc-4.0.3 -dumpspecs, but is not listed in the documentation.

Sure it is: gcc/gcc/config/rs6000/rs6000.c, line #s about
1250 and further ;-)

It's supposed to be in the info manual too, if not, please
file a PR; looks good to me though.

> There is also -me500, while -me200 seems to be known only
> to gas but not gcc.

There is no -mcpu=e500.  -me500 is a GAS option.
GCC's -mcpu= options generally take specific CPU names
as parameter; I suppose it would make sense to add e200
et. al.

> What would be the right options to pass on e200 and on
> pa6t?

The best thing would be to add GCC -mcpu= options.  For
now, you're probably best of with -mcpu=powerpc and
-mcpu=powerpc64 resp., i.e. the "blended models".  This
is a good option for multiplatform kernels too; add -mtune=
to optimise for a specific core, but it will *work* on
the whole family.


Segher

  parent reply	other threads:[~2007-04-12 19:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 11:15 [patch 3/3] cell: prevent alignment interrupt on local store Akinobu Mita
2007-04-10 12:52 ` Segher Boessenkool
2007-04-11  3:06   ` Akinobu Mita
2007-04-10 21:22 ` Benjamin Herrenschmidt
2007-04-11  2:56   ` Akinobu Mita
2007-04-11  3:30     ` Benjamin Herrenschmidt
2007-04-11 21:03       ` Segher Boessenkool
2007-04-12  4:23         ` Olaf Hering
2007-04-12  5:26           ` Benjamin Herrenschmidt
2007-04-12  6:33             ` Olaf Hering
2007-04-12  6:38               ` Benjamin Herrenschmidt
2007-04-12  8:31                 ` Gabriel Paubert
2007-04-12  8:48                   ` Benjamin Herrenschmidt
2007-04-12  6:50           ` Segher Boessenkool
2007-04-12  6:57             ` [Cbe-oss-dev] " Michael Ellerman
2007-04-12  7:07               ` Segher Boessenkool
2007-04-12 18:43           ` Arnd Bergmann
2007-04-12 18:55             ` Arnd Bergmann
2007-04-12 19:57               ` Segher Boessenkool
2007-04-12 19:52             ` Segher Boessenkool
2007-04-12 13:01   ` [RFC, PATCH] selection of CPU optimization Arnd Bergmann
2007-04-12 16:45     ` Kumar Gala
2007-04-12 17:26       ` [Cbe-oss-dev] " Arnd Bergmann
2007-04-12 18:17         ` Kumar Gala
2007-04-12 19:25           ` Arnd Bergmann
2007-04-12 20:04           ` Olof Johansson
2007-04-12 20:01             ` Segher Boessenkool
2007-04-12 20:22               ` Olof Johansson
2007-04-12 20:22                 ` Segher Boessenkool
2007-04-12 19:50         ` Segher Boessenkool [this message]
2007-04-13  0:10           ` Arnd Bergmann
2007-04-13  2:03             ` Olof Johansson
2007-04-13 18:43             ` Segher Boessenkool

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=e5b10849669a764f002d1926838edc76@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=cbe-oss-dev@ozlabs.org \
    --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;
as well as URLs for NNTP newsgroup(s).