From: Scott Wood <scottwood@freescale•com>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev@lists•ozlabs.org
Subject: Re: Pull request: scottwood/linux.git next
Date: Wed, 14 Aug 2013 12:02:39 -0500 [thread overview]
Message-ID: <1376499759.31636.15.camel@snotra.buserror.net> (raw)
In-Reply-To: <1376453881.4255.57.camel@pasglop>
On Wed, 2013-08-14 at 14:18 +1000, Benjamin Herrenschmidt wrote:
> On Thu, 2013-08-08 at 17:45 -0500, Scott Wood wrote:
> > powerpc/e500: Update compilation flags with core specific
> > options
>
> This breaks the build for my FSL test configs. For some reason gcc 4.7.3
> doesn't know about -mcpu=e5500
Ugh. I guess that's what I get for using toolchains provided internally
rather than building them myself -- though it doesn't help that the GCC
people love finding new ways to break building GCC without libc (why
doesn't --without-headers automatically disable any component that
requires libc headers?), and usually respond to bug reports with "go run
crosstool and leave us alone". It looks like e5500 support is in 4.8.1,
but I can't actually get it to build (libdecnumber wants to
#include_next <stdlib.h> and can't be disabled -- arm64 toolchain built
fine with the similar configure options). I don't know about earlier
versions.
> Additionally, on 64-bit, that means one can no longer make a kernel that
> does both A2 and e5500...
Other than the toolchain issue, I'm not sure how this is worse than it
was before, when such a kernel would have had -Wa,-me500 forced.
What -mcpu value should be used in such a combined kernel?
> I'm reverting that crap patch, please make such optimizations CONFIG_*
> options like power5...7
Speaking of crap patches, those config options don't limit themselves to
book3s and thus we're now getting CONFIG_GENERIC_CPU (and thus
-mtune=power7) on e5500 builds.
-Scott
next prev parent reply other threads:[~2013-08-14 17:02 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 22:45 Pull request: scottwood/linux.git next Scott Wood
2013-08-09 6:03 ` Benjamin Herrenschmidt
2013-08-09 14:43 ` Kumar Gala
2013-08-09 16:30 ` Scott Wood
2013-08-14 4:18 ` Benjamin Herrenschmidt
2013-08-14 17:02 ` Scott Wood [this message]
2013-08-14 21:01 ` Benjamin Herrenschmidt
2013-08-19 22:56 ` Scott Wood
2013-08-19 23:47 ` Benjamin Herrenschmidt
2013-08-19 23:49 ` Josh Boyer
2013-08-20 0:49 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2019-11-17 9:44 Scott Wood
2019-10-22 23:21 Scott Wood
2019-10-31 2:01 ` Jason Yan
2019-11-01 17:01 ` Scott Wood
2019-11-04 2:36 ` Jason Yan
2019-11-02 10:38 ` Michael Ellerman
2019-11-04 2:38 ` Jason Yan
2019-11-13 9:23 ` Michael Ellerman
2019-11-14 6:00 ` Jason Yan
2018-12-22 4:42 Scott Wood
2018-12-22 10:50 ` christophe leroy
2018-12-22 20:01 ` Scott Wood
2018-12-23 13:13 ` Michael Ellerman
2018-12-24 2:09 ` Scott Wood
2018-12-27 13:10 ` Christoph Hellwig
2018-12-28 0:03 ` Scott Wood
2018-10-23 0:22 Scott Wood
2018-08-11 5:29 Scott Wood
2018-01-21 7:55 Scott Wood
2018-01-23 5:24 ` Michael Ellerman
2017-08-29 4:20 Scott Wood
2017-05-06 3:42 Scott Wood
2017-01-27 23:53 Scott Wood
2017-02-17 11:08 ` Scott Wood
2017-02-18 8:00 ` Michael Ellerman
2016-12-12 8:17 Scott Wood
2016-12-13 15:49 ` Aneesh Kumar K.V
2016-12-13 18:34 ` Aneesh Kumar K.V
2016-09-27 22:08 Scott Wood
2016-07-21 17:09 Scott Wood
2016-05-17 1:37 Scott Wood
2016-05-19 12:35 ` Michael Ellerman
2016-03-12 3:15 Scott Wood
2016-03-15 0:19 ` Michael Ellerman
2016-03-15 7:01 ` Scott Wood
2016-03-15 9:07 ` Michael Ellerman
2016-03-15 17:50 ` Scott Wood
2016-03-15 10:27 ` Christophe Leroy
2016-01-04 21:38 Scott Wood
2016-01-14 13:05 ` Michael Ellerman
2015-10-28 21:56 Scott Wood
2015-08-18 4:30 Scott Wood
2015-08-26 14:14 ` Scott Wood
2015-08-27 1:14 ` Michael Ellerman
2015-06-05 23:06 Scott Wood
2015-04-02 22:47 Scott Wood
2015-02-03 17:20 Scott Wood
2015-02-04 0:58 ` Michael Ellerman
2015-02-04 1:05 ` Scott Wood
2015-02-04 2:25 ` Michael Ellerman
2014-11-18 5:20 Scott Wood
2014-09-22 22:21 Scott Wood
2014-09-23 3:52 ` Bob Cochran
2014-09-23 5:45 ` Scott Wood
2014-09-23 10:47 ` Joakim Tjernlund
2014-09-23 12:37 ` Scott Wood
2014-09-23 16:19 ` Bob Cochran
2014-10-03 19:52 ` Scott Wood
2014-10-03 23:06 ` Stephen Rothwell
2014-08-01 19:54 Scott Wood
2014-07-03 0:51 Scott Wood
2014-03-20 4:25 Scott Wood
2014-03-23 23:16 ` Benjamin Herrenschmidt
2014-03-23 23:33 ` Benjamin Herrenschmidt
2014-03-25 1:09 ` Scott Wood
2013-10-29 2:44 Scott Wood
2013-10-29 3:05 ` Scott Wood
2013-08-24 1:07 Scott Wood
2013-08-26 15:48 ` Scott Wood
2013-07-01 23:43 Scott Wood
2013-07-02 7:43 ` Benjamin Herrenschmidt
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=1376499759.31636.15.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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