linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Paul Mackerras <paulus@samba.org>
Cc: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] Set cpu explicitly in kernel compiles
Date: Thu, 5 May 2005 08:24:09 -0400	[thread overview]
Message-ID: <7de437cded3ef3b030898889bf65e8c9@embeddededge.com> (raw)
In-Reply-To: <17017.44421.790813.918463@cargo.ozlabs.ibm.com>


On May 5, 2005, at 1:22 AM, Paul Mackerras wrote:
> If you think we should have -mcpu=xxx on the command line for 4xx,
> 44x, 8xx, etc., then that's fine, but that is a separate problem from
> what my patch was addressing (one which my patch might make it easier
> to fix, though).

I think that is exactly what we want, although I don't know how that is
separate from the patch you sent.  My original comment was the patch
fixes the problem for only one of the cpu cores, not all of them.  Which
then led into the subsequent suggestion of making the biarch work
like the past compilers, and we must specific the flags for POWER4
instead of the other way around.  Without explicit -mcpu flags, the
existing compiler behavior is just fine .....  but, I guess I'd be 
standing
in the way of progress to want this :-)

Thanks.

	-- Dan

  reply	other threads:[~2005-05-05 12:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04  7:05 [PATCH] Set cpu explicitly in kernel compiles Paul Mackerras
2005-05-04 11:28 ` Dan Malek
2005-05-04 15:34   ` Tom Rini
2005-05-04 16:06     ` Chris Friesen
2005-05-04 21:36   ` Paul Mackerras
2005-05-04 23:21     ` Dan Malek
2005-05-05  4:00       ` Paul Mackerras
2005-05-05  4:12         ` Tom Rini
2005-05-05  4:44           ` Paul Mackerras
2005-05-05  4:47             ` Tom Rini
2005-05-05  5:22               ` Paul Mackerras
2005-05-05 12:24                 ` Dan Malek [this message]
2005-05-05 14:00                   ` Kumar Gala
2005-05-05 14:23                     ` Tom Rini
2005-05-05 15:12                       ` Kumar Gala
2005-05-05 15:27                         ` Tom Rini
2005-05-05 16:22                           ` Kumar Gala
2005-05-05 16:29                             ` Tom Rini
2005-05-06 14:44                 ` Segher Boessenkool
2005-05-06 14:53                   ` Tom Rini
2005-05-06 15:28                     ` Segher Boessenkool
2005-05-06 15:34                       ` Tom Rini
2005-05-06 15:47                     ` Kumar Gala
2005-05-05 12:12             ` Dan Malek
2005-05-04 13:45 ` Kumar Gala
2005-05-04 15:28   ` Tom Rini
2005-07-03 17:29 ` Olaf Hering
2005-07-03 18:32   ` Tom Rini
2005-07-05 18:14     ` Olaf Hering
2005-07-05 19:47       ` Tom Rini
2005-07-05 19:54         ` Olaf Hering
2005-07-05 19:58           ` Tom Rini
2005-07-05 20:17             ` Olaf Hering
2005-07-05 20:27             ` Olaf Hering
2005-07-05 21:22               ` Tom Rini
2005-07-06  6:38                 ` Olaf Hering
2006-04-02 19:40 ` Olaf Hering
2006-04-06  4:37   ` Paul Mackerras
2006-04-11 18:42     ` Olaf Hering

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=7de437cded3ef3b030898889bf65e8c9@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=trini@kernel.crashing.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).