This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC 4.3.0 Status Report (2008-02-14)
- From: "Richard Guenther" <richard dot guenther at gmail dot com>
- To: "Joel Sherrill" <joel dot sherrill at oarcorp dot com>
- Cc: "Alexandre Pereira Nunes" <alexandre dot nunes at gmail dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Thu, 14 Feb 2008 22:16:41 +0100
- Subject: Re: GCC 4.3.0 Status Report (2008-02-14)
- References: <47B48866.6030300@gmail.com> <47B48B87.7090501@oarcorp.com>
On Thu, Feb 14, 2008 at 7:42 PM, Joel Sherrill
<joel.sherrill@oarcorp.com> wrote:
>
> Alexandre Pereira Nunes wrote:
> > Also regarding ARM, PR31849
> > (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31849
> > <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31849>) is a show stopper,
> > at least for some embedded bare metal targets, i.e. arm-elf and
> > arm-none-eabi.
> >
> > Until size optimization at least matches gcc 4.2, gcc 4.3 will have very
> > limited audience there. I'm not aware of gcc internals in order to help
> > with a fix, but I'm available to help testing, should anyone requires that.
> >
> >
> The m68k/coldfire is suffering from this regression the
> RTEMS community really would like to see resolved.
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35088
>
> I just emailed everyone who touched the m68k port since
> last summer a charity appeal. :-D
No m86k triple is primary or secondary target, so this is not going to
block the release.
But there was plenty of time for the rtems/m68k people to look at problems with
their port.
Richard.