Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] Revert "cross-canadian: Handle powerpc linux verses linux-gnuspe"
Date: Tue, 21 Jan 2014 09:59:13 -0800	[thread overview]
Message-ID: <1877769.UoNhV5qYuS@leo> (raw)
In-Reply-To: <1390044007.14987.151.camel@ted>

[-- Attachment #1: Type: text/plain, Size: 1572 bytes --]

On Saturday, January 18, 2014 11:20:07 AM Richard Purdie wrote:
> On Fri, 2014-01-17 at 14:43 +0000, alexandru.sardan@freescale.com wrote:
> > e500v1/v2 uses SPE to handle floating point operations
> > using general purpose regs.
> > So using the non-SPE compiler with SPE libraries won't work.
> > However the soft-fp libraries are compatible with the e500
> > ABI (with a considerable performance penalty).
> > 
> > From what I can see, eglibc is built with SPE. So GCC should
> > be built also for SPE (target powerpc-poky-linux-gnuspe).
> 
> The key question is this:
> 
> Can one gcc binary generate code for both non-SPE and SPE targets,
> assuming its pointed at an appropriate sysroot containing appropriate
> libraries?
> 
> If we can have one such binary, how do we configure it? If we can't, we
> need to redo the way gcc-cross-canadian is working on powerpc.
> 

I think gcc can generate the code all you would need is option, real problem
is gcc runtime which will need different set of libraries and init files.


> The change there was to have one gcc for each different target
> architecture rather than each "tune" since that was horribly
> inefficient.
> 

We dont need specific to tune but spe is ABI identifier that should be treated 
differently then defaul tunes IMO

> Cheers,
> 
> Richard
> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
-Khem

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      parent reply	other threads:[~2014-01-21 17:59 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
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 [this message]

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=1877769.UoNhV5qYuS@leo \
    --to=raj.khem@gmail.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