From: wino <wino@piments.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: Martin Guy <martinwguy@gmail.com>,
crossgcc@sourceware.org, yann.morin.1998@anciens.enib.fr
Subject: Re: crosstool-ng: cross compiler for -mach=arm4vt (Cirrus Logic EP93xx target)
Date: Wed, 09 Sep 2009 19:26:00 -0000 [thread overview]
Message-ID: <4AA8014B.3010906@piments.com> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901CBEAFE@mi8nycmail19.Mi8.com>
On Wednesday, September 09, 2009 4:01 AM, Martin Guy wrote:
>>>> (maverick) Use specific FPU
>>>> Floating point: ---> hardware (FPU)
>> Don't do that! :) Mainline GCC's code generation for Maverick is
>> completely broken, glibc needs patches, binutils barfs on some GCC
>> output for C++, and the FPU itself is full of hardware timing bugs
>> that GCC fails miserably to work around.
>> I have a set of working GCC patches for C, and OE have collected the
>> glibc and binutils patches but I've never heard of anyone getting a
>> fully working rootfs yet.
>
Hi,
would it be possible to provide links to these patch sets so that they
could be included in ct-ng?
IIRC you recommend 4.2.2 rather than 4.3.x , is that correct?
regards.
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2009-09-09 19:26 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 22:48 H Hartley Sweeten
2009-09-09 11:01 ` Martin Guy
2009-09-09 18:06 ` H Hartley Sweeten
2009-09-09 19:26 ` wino [this message]
2009-09-11 19:33 ` Martin Guy
2009-09-11 21:57 ` ng
2009-09-11 22:12 ` wino
2009-09-11 22:20 ` Martin Guy
2009-09-12 20:18 ` Khem Raj
2009-09-13 13:15 ` Martin Guy
2009-09-13 15:55 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 20:42 H Hartley Sweeten
2009-09-08 21:17 ` Yann E. MORIN
2009-09-08 21:31 ` Matthias Kaehlcke
2009-09-09 8:39 ` Steve Papacharalambous
2009-09-09 11:21 ` Martin Guy
2009-09-09 15:30 ` Steve Papacharalambous
2009-09-09 13:42 ` ng
2009-09-09 17:26 ` H Hartley Sweeten
2009-09-11 10:29 ` Martin Guy
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=4AA8014B.3010906@piments.com \
--to=wino@piments.com \
--cc=crossgcc@sourceware.org \
--cc=hartleys@visionengravers.com \
--cc=martinwguy@gmail.com \
--cc=yann.morin.1998@anciens.enib.fr \
/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).