From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11310 invoked by alias); 17 Feb 2015 18:15:26 -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 11257 invoked by uid 48); 17 Feb 2015 18:15:22 -0000 From: "hp at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/65093] New: [5 Regression] 26_numerics/random/binomial_distribution/operators/values.cc times out Date: Tue, 17 Feb 2015 18:15:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: 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 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: 2015-02/txt/msg01920.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65093 Bug ID: 65093 Summary: [5 Regression] 26_numerics/random/binomial_distribution/operators/val ues.cc times out Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: hp at gcc dot gnu.org Host: x86_64-linux-gnu Target: cris-elf This test used to pass. Since a commit in the range (220738:220744]it fails for cris-elf as follows: Running /tmp/hpautotest-gcc1/gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ... [...] WARNING: program timed out. FAIL: 26_numerics/random/binomial_distribution/operators/values.cc execution test (no further information in the .log file) There were no changes to libstdc++-v3 in the revision range. Apparently the middle-end changed such that code quality suffered enough that the test now times out on the machine where I run autototests. I'm going to bisect the middle-end changes in the revision range and inspect the code.