public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/44576] [4.5/4.6 Regression] testsuite/gfortran.dg/zero_sized_1.f90 with huge compile time on prefetching + peeling Date: Sat, 26 Jun 2010 14:25:00 -0000 [thread overview] Message-ID: <20100626142521.13248.qmail@sourceware.org> (raw) In-Reply-To: <bug-44576-18712@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from rguenth at gcc dot gnu dot org 2010-06-26 14:25 ------- I now see compile-time on polyhedron sky-rocketed with enabling prefetching at -O3 by default. See http://gcc.opensuse.org/c++bench/polyhedron/polyhedron-summary.txt-1-0.html This isn't acceptable - please work on this. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44576
next prev parent reply other threads:[~2010-06-26 14:25 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-18 7:51 [Bug middle-end/44576] New: testsuite/gfortran.dg/zero_sized_1.f90 with huge compile time on prefetching+peeling borntraeger at de dot ibm dot com 2010-06-18 7:59 ` [Bug middle-end/44576] testsuite/gfortran.dg/zero_sized_1.f90 with huge compile time on prefetching + peeling borntraeger at de dot ibm dot com 2010-06-18 10:52 ` [Bug middle-end/44576] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org 2010-06-24 21:44 ` rguenth at gcc dot gnu dot org 2010-06-25 9:03 ` borntraeger at de dot ibm dot com 2010-06-25 17:08 ` changpeng dot fang at amd dot com 2010-06-26 14:25 ` rguenth at gcc dot gnu dot org [this message] 2010-06-26 20:30 ` borntraeger at de dot ibm dot com 2010-06-27 9:16 ` rguenth at gcc dot gnu dot org 2010-06-27 9:17 ` rguenth at gcc dot gnu dot org 2010-06-27 11:09 ` borntraeger at de dot ibm dot com 2010-06-27 11:20 ` rguenth at gcc dot gnu dot org 2010-06-29 0:07 ` changpeng dot fang at amd dot com 2010-06-29 0:49 ` changpeng dot fang at amd dot com 2010-06-30 0:23 ` changpeng dot fang at amd dot com 2010-06-30 0:36 ` changpeng dot fang at amd dot com 2010-07-01 0:34 ` changpeng dot fang at amd dot com 2010-07-02 16:34 ` spop at gcc dot gnu dot org 2010-07-02 23:58 ` changpeng dot fang at amd dot com 2010-07-07 18:15 ` spop at gcc dot gnu dot org 2010-07-07 19:00 ` changpeng dot fang at amd dot com 2010-07-09 1:59 ` changpeng dot fang at amd dot com 2010-07-09 23:09 ` spop at gcc dot gnu dot org 2010-07-09 23:12 ` spop at gcc dot gnu dot 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=20100626142521.13248.qmail@sourceware.org \ --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: linkBe 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).