From: Scott Wood <scottwood@freescale•com>
To: Rojhalat Ibrahim <imr@rtschenk•de>
Cc: Catalin Udma <catalin.udma@freescale•com>, linuxppc-dev@lists•ozlabs.org
Subject: Re: [PATCH 3/4] powerpc/booke64: Use appropriate -mcpu
Date: Thu, 22 Aug 2013 09:18:27 -0500 [thread overview]
Message-ID: <1377181107.5029.91.camel@snotra.buserror.net> (raw)
In-Reply-To: <1753626.1M86qx3vEi@pcimr>
On Thu, 2013-08-22 at 15:56 +0200, Rojhalat Ibrahim wrote:
> Just out of curiosity: What's the difference (if any) between -mcpu=e500mc64
> and -mcpu=e5500? AFAIK -mcpu=e500mc64 is supported by gcc since at least
> version 4.6 whereas -mcpu=e5500 is only supported since gcc 4.8. But is there
> actually any difference?
I had asked our compiler person that before sending... the answer
wasn't very clear, but when I asked whether there was any benefit for
the kernel specifying e5500 (requiring an extra fallback check) he said
"probably not". Eventually they'll probably just become aliases for the
same thing. Currently they do have separate .md files though, so
they're not identical.
-Scott
next prev parent reply other threads:[~2013-08-22 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 2:12 [PATCH 0/4] powerpc/e500: rework compiler flags Scott Wood
2013-08-21 2:12 ` [PATCH 1/4] powerpc: Convert some mftb/mftbu into mfspr Scott Wood
2013-08-21 2:12 ` [PATCH 2/4] powerpc/85xx: Remove -Wa,-me500 Scott Wood
2013-08-21 2:12 ` [PATCH 3/4] powerpc/booke64: Use appropriate -mcpu Scott Wood
2013-08-22 13:56 ` Rojhalat Ibrahim
2013-08-22 14:18 ` Scott Wood [this message]
2013-08-21 2:12 ` [PATCH 4/4] powerpc/e500: Set -mcpu flag for 32-bit e500 Scott Wood
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=1377181107.5029.91.camel@snotra.buserror.net \
--to=scottwood@freescale$(echo .)com \
--cc=catalin.udma@freescale$(echo .)com \
--cc=imr@rtschenk$(echo .)de \
--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