This is the mail archive of the
mailing list for the GCC project.
Re: GCC 5 Status Report (2015-01-08), Stage 4 to start soon
- From: Jeff Law <law at redhat dot com>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>, Christian Bruel <christian dot bruel at st dot com>, ramana Radhakrishnan <Ramana dot Radhakrishnan at arm dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Jakub Jelinek <jakub at redhat dot com>
- Date: Fri, 09 Jan 2015 09:52:43 -0700
- Subject: Re: GCC 5 Status Report (2015-01-08), Stage 4 to start soon
- Authentication-results: sourceware.org; auth=none
- References: <20150108103229 dot GB1405 at tucnak dot redhat dot com> <54AFB792 dot 8040208 at st dot com> <54AFF49F dot 8080707 at oarcorp dot com>
On 01/09/15 08:32, Joel Sherrill wrote:
I can't really test coldfire, but Andreas's comment indicates we can
just disable that pattern.
Piling on here. For RTEMS, we have 5 targets with GCC PRs reported.
Ignoring the avr and m32c, we have arm, m68k and nios2 all with
regressions since 4.9. I think these PRs are important enough
that they should get consideration:
+ arm: ICE GCC PR64460 segfault for -O2 and xscale
+ m68k: GCC PR64461 invalid code for all Coldfires
Feel free to assign it to me. Not sure if it's strictly a regression,
but I'd argue that it's broken enough to warrant fixing regardless of
what stage we're in. If indeed it's as simple as disabling that
pattern, the chances for collateral damage are trivially small.