http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58221
Bug ID: 58221
Summary: [4.9 Regression]: Immense amount of execution
regressions and increased test-time for cris-elf
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: regression
Assignee: unassigned at gcc dot gnu.org
Reporter: hp at gcc dot gnu.org
Host: x86_64-unknown-linux-gnu
Target: cris-axis-elf
I see a LOT of execution regressions introduced in the interval
(201874:201887], too many to list them individually here. At r201887 it's
regress-4951, an increase of about 4500! Maybe every executing test. Also, an
an increase in build-test time from to 3:39:09elapsed to 44:27:48elapsed (yup
about two days) apparently due to many tests infinitely looping and timing out.
At r201919 it seems pretty much the same this far.
Things were bad to start with, status regress-446 at r201874, where there used
to be regress-7 as late as r201859. Those 400+ regressions were in libstdc++
and probably the same as observed by others, due to insufficient testing of the
pass changes, but those patches were reverted at r201887. The failing tests
are all over the supported languages for this target; C, ObjC, C++ and Fortran.
I'm entering this PR to track the issue. Further details to follow.
First suspect is r201883, so first informed-bisect triage point will be
r201882.
