From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12599 invoked by alias); 23 Aug 2013 01:21:34 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 12584 invoked by uid 48); 23 Aug 2013 01:21:33 -0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug regression/58221] New: [4.9 Regression]: Immense amount of execution regressions and increased test-time for cris-elf Date: Fri, 23 Aug 2013 01:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: regression X-Bugzilla-Version: 4.7.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: hp at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cf_gcchost cf_gcctarget Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-08/txt/msg01178.txt.bz2 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.