From: "Carlos O'Donell" <carlos@systemhalted.org>
To: "Ryan S. Arnold" <ryan.arnold@gmail.com>
Cc: acrux <acrux_it@libero.it>, libc-ports@sourceware.org
Subject: Re: [PATCH] powerpc: 405/440/464/476 support and optimizations
Date: Fri, 20 Jan 2012 18:03:00 -0000 [thread overview]
Message-ID: <CADZpyizC9hFyb-frt1-4jvhpRtywU_LEiaSWk=KyLm-Z+wLuOg@mail.gmail.com> (raw)
In-Reply-To: <CAAKybw9RLGE93P5OQpf0NSd-vmuG+JbHnKAQF8afUAqL9rv5ig@mail.gmail.com>
On Fri, Jan 20, 2012 at 10:52 AM, Ryan S. Arnold <ryan.arnold@gmail.com> wrote:
> Does the machine you're building this toolchain on understand the
> 440fp instruction set? If not then the loader is likely encountering
> a sigill.
There are some known problems in this area which Mentor Graphics ESD
has been fixing and submitting upstream.
They mainly have to do with the graphics and string instructions that
aren't uniformly supported and gcc doesn't know when not to use some
of these instructions.
If your goal is to succeed at compiling things for your target then I
would start here:
http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/platforms/power-gnulinux
or just command-line tools for free, click under "Power Architecture
Processors"->"Download the GNU/Linux release"
http://www.mentor.com/embedded-software/sourcery-tools/sourcery-codebench/editions/lite-edition/
They are all based on the open-source tools but with enhancements to
fix problems like the one you ran into.
I'm part of the team that produces these toolchains so I'm biased :-)
Cheers,
Carlos.
next prev parent reply other threads:[~2012-01-20 18:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 17:34 Luis Machado
2010-09-03 14:45 ` Ryan Arnold
2010-09-03 15:00 ` Luis Machado
2010-10-04 18:54 ` Luis Machado
2010-12-13 20:26 ` Ryan Arnold
2011-01-18 13:16 ` Ryan Arnold
2011-01-25 21:32 ` Joseph S. Myers
2012-01-18 20:31 ` acrux@cruxppc.org
2012-01-19 19:35 ` Carlos O'Donell
2012-01-20 14:24 ` acrux
2012-01-20 15:52 ` Ryan S. Arnold
2012-01-20 18:03 ` Carlos O'Donell [this message]
2012-01-23 0:41 ` acrux
2012-01-23 15:48 ` Ryan S. Arnold
2012-01-24 16:47 ` acrux
2012-01-24 17:20 ` Ryan S. Arnold
2012-01-24 17:41 ` acrux
2012-01-24 17:59 ` Ryan S. Arnold
2012-02-18 2:06 ` acrux
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='CADZpyizC9hFyb-frt1-4jvhpRtywU_LEiaSWk=KyLm-Z+wLuOg@mail.gmail.com' \
--to=carlos@systemhalted.org \
--cc=acrux_it@libero.it \
--cc=libc-ports@sourceware.org \
--cc=ryan.arnold@gmail.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).