public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/48283] gcc.dg/graphite/block-[3478].c timeouts
Date: Fri, 25 Mar 2011 13:02:00 -0000	[thread overview]
Message-ID: <bug-48283-4-Ch4n7vcpgQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48283-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48283

--- Comment #2 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> 2011-03-25 12:35:03 UTC ---
> --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-25 12:26:55 UTC ---
> Just to clarify - runtime or compile-time issue?  I see the testcases
> operate on 100^3 arrays - certainly not small for very slow HW.

Compile time, runtime for block-3.exe is 0.06 s even on the R10k
machine.

> I'd say skip graphite tests completely for !run_expensive_tests for now.

I'd rather tag the four culprits only for the moment to keep some
coverage.

    Rainer


  parent reply	other threads:[~2011-03-25 12:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-25 11:47 [Bug testsuite/48283] New: " ro at gcc dot gnu.org
2011-03-25 13:00 ` [Bug testsuite/48283] " rguenth at gcc dot gnu.org
2011-03-25 13:02 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2011-03-25 14:06 ` ro at gcc dot gnu.org
2011-05-18  0:01 ` michael.hope at linaro dot org
2013-07-14  5:33 ` spop 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-48283-4-Ch4n7vcpgQ@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).