From: Phil Blundell <pb@pbcl.net>
To: "alexandru.sardan@freescale.com" <alexandru.sardan@freescale.com>
Cc: "catalin.udma@freescale.com" <catalin.udma@freescale.com>,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe"
Date: Fri, 24 Jan 2014 20:56:01 +0000 [thread overview]
Message-ID: <1390596961.24755.21.camel@e130.pbcl.net> (raw)
In-Reply-To: <c5873e086bd941e68daa26cbcdca573e@BLUPR03MB357.namprd03.prod.outlook.com>
On Thu, 2014-01-23 at 18:22 +0000, alexandru.sardan@freescale.com wrote:
> [Alex Sardan] No. The more generic target powerpc-none-linux will not
> generate SPE code and the powerpc-none-linux-gnuspe target that generates
> SPE will not be able to generate Altivec.
Why not? As far as I can tell from the gcc configury, the target string
only affects the defaults (i.e. powerpc-*-linux gets -mno-spe
-mno-altivec, powerpc-*-linuxaltivec gets -maltivec -mno-spec, and
powerpc-*-linuxspe gets -mno-altivec -mspe). There doesn't seem to be
any real impact beyond this that would make the compiler binary
fundamentally incapable of generating either type of instruction if you
pass the appropriate options on the command line.
p.
next prev parent reply other threads:[~2014-01-24 20:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 14:48 [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe" David Nyström
2014-01-10 15:15 ` Richard Purdie
2014-01-13 12:37 ` David Nyström
2014-01-13 12:41 ` Richard Purdie
2014-01-14 13:23 ` David Nyström
2014-01-17 14:43 ` alexandru.sardan
2014-01-18 11:20 ` Richard Purdie
2014-01-21 17:39 ` alexandru.sardan
2014-01-21 17:43 ` Richard Purdie
2014-01-23 18:22 ` alexandru.sardan
2014-01-24 15:37 ` Richard Purdie
2014-01-24 20:56 ` Phil Blundell [this message]
2014-01-28 14:03 ` alexandru.sardan
2014-01-29 11:38 ` Richard Purdie
2014-01-31 17:53 ` alexandru.sardan
2014-01-31 18:07 ` Richard Purdie
2014-01-31 18:17 ` alexandru.sardan
2014-02-11 10:07 ` David Nyström
2014-02-26 18:29 ` alexandru.sardan
2014-02-26 22:37 ` David Nyström
2014-02-27 12:21 ` alexandru.sardan
2014-01-21 17:59 ` Khem Raj
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=1390596961.24755.21.camel@e130.pbcl.net \
--to=pb@pbcl.net \
--cc=alexandru.sardan@freescale.com \
--cc=catalin.udma@freescale.com \
--cc=openembedded-core@lists.openembedded.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