This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Please don't deprecate i386 for GCC 4.8
- From: Ralf Corsepius <ralf dot corsepius at googlemail dot com>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>
- Cc: Robert Dewar <dewar at adacore dot com>, Ralf Corsepius <ralf dot corsepius at googlemail dot com>, Richard Biener <richard dot guenther at gmail dot com>, Cynthia Rempel <cynt6007 at vandals dot uidaho dot edu>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Sun, 16 Dec 2012 04:50:16 +0100
- Subject: Re: Please don't deprecate i386 for GCC 4.8
- References: <gvih7g1t8qupsjlfpa369bnv.1355594497885@email.android.com>
On 12/15/2012 07:02 PM, Joel Sherrill wrote:
I did test i386-rtems in the past few months but it had a build breakage and I filed a PR. That issue was resolved but at that point about 1/4 of the rtems targets failed to compile.
You likely are referring to
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55175
Yes, this bug is fixed, but a follow-up discussion[1] of this
as resulted into what I had called "the known and yet unresolved
soft-float/i386" issues earlier in this thread.
Ralf
[1] Start around
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55175#c9
Todate, I know there are at least 2 (possibly 3) bugs interacting, one
(possibly 2) in GCC and one in newlib, which render the i386/softfloat
multilib variant of i386-rtems GCC non-functional.