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:12:39 -0400 [thread overview]
Message-ID: <74e4ebe2933fc8b81b86b8e645a98f1c@embeddededge.com> (raw)
In-Reply-To: <17017.42136.824607.253146@cargo.ozlabs.ibm.com>
On May 5, 2005, at 12:44 AM, Paul Mackerras wrote:
> The problem only comes up if you configure gcc4 as biarch. I can't
> imagine anyone building a biarch compiler for 4xx or 8xx. :)
Why not? I've never built a "special" compiler for any development
work, and am very likely to use the default compiler installed on
my YDL system (which could likely be a G5) for building any
embedded PowerPC software.
> So yes, only CONFIG_6xx is affected by biarch gcc4 assuming POWER4.
> Other families would only be affected if you were using a generic
> gcc4, which won't work at present anyway, since we don't add
> -mcpu=xxx.
What do you mean by "won't work"? The compiler simply refuses
or builds for a POWER4 because we don't have the proper -mcpu
flags?
Thanks.
-- Dan
next prev parent reply other threads:[~2005-05-05 12:12 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
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 [this message]
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=74e4ebe2933fc8b81b86b8e645a98f1c@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 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.