public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.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	[thread overview]
Message-ID: <bug-65093-4@http.gcc.gnu.org/bugzilla/> (raw)

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.


             reply	other threads:[~2015-02-17 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-17 18:15 hp at gcc dot gnu.org [this message]
2015-02-18 11:14 ` [Bug middle-end/65093] " rguenth at gcc dot gnu.org
2015-02-18 11:41 ` jakub at gcc dot gnu.org
2015-02-19  1:22 ` [Bug testsuite/65093] 26_numerics/random/binomial_distribution/operators/values.cc times out on slow targets hp at gcc dot gnu.org
2015-02-19 19:30 ` hp at gcc dot gnu.org
2015-02-19 19:41 ` hp at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-65093-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).