public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belyshev at depni dot sinp dot msu dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug testsuite/35406] gfortran.dg/ldist-1.f90 and gcc.dg/tree-ssa/ldist-4.c don't work Date: Thu, 06 Mar 2008 18:35:00 -0000 [thread overview] Message-ID: <20080306183421.22070.qmail@sourceware.org> (raw) In-Reply-To: <bug-35406-682@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from belyshev at depni dot sinp dot msu dot ru 2008-03-06 18:34 ------- Both are testsuite bugs, apparently. ldist-1.f90 scans for: ! { dg-final { scan-tree-dump-times "distributed: split to 4 loops" 1 "ldist" } } and the dump output is: "Loop 1 distributed: split to 5 loops." And ldist-4.c is even xfailed in a weird way: /* We used to distribute also innermost loops, but these could produce too much code in the outer loop, degrading performance of scalar code. So this test is XFAILed because the cost model of the stand alone distribution pass has evolved. */ /* { dg-final { scan-tree-dump-times "distributed: split to 2 loops" 0 "ldist" } } */ and it works now: FIXME: Loop 1 not distributed: it has more than two basic blocks. Loop 2 distributed: split to 2 loops. -- belyshev at depni dot sinp dot msu dot ru changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |belyshev at depni dot sinp | |dot msu dot ru Severity|normal |trivial Component|tree-optimization |testsuite Last reconfirmed|2008-03-04 17:14:36 |2008-03-06 18:34:21 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35406
next prev parent reply other threads:[~2008-03-06 18:35 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-02-29 15:20 [Bug tree-optimization/35406] New: " hjl dot tools at gmail dot com 2008-03-04 17:15 ` [Bug tree-optimization/35406] " ismail at namtrac dot org 2008-03-06 18:35 ` belyshev at depni dot sinp dot msu dot ru [this message] 2008-03-09 23:47 ` [Bug testsuite/35406] " danglin at gcc dot gnu dot org 2008-03-10 0:09 ` jvdelisle at gcc dot gnu dot org 2008-03-14 3:49 ` jvdelisle at gcc dot gnu dot org 2008-03-14 3:51 ` jvdelisle at gcc dot gnu dot org 2008-03-14 4:04 ` jvdelisle at gcc dot gnu dot org 2008-03-14 5:01 ` jvdelisle at gcc dot gnu dot org 2008-03-14 5:07 ` jvdelisle at gcc dot gnu dot org 2008-03-14 5:21 ` hjl dot tools at gmail dot com 2008-03-14 6:38 ` ubizjak at gmail dot com 2008-03-14 11:29 ` hp at gcc dot gnu dot org 2008-03-14 12:44 ` ubizjak at gmail dot com 2008-03-14 12:55 ` ubizjak at gmail dot com 2008-03-14 13:49 ` hp at gcc dot gnu dot org 2008-03-14 14:19 ` uros at gcc dot gnu dot org 2008-03-14 14:26 ` ubizjak at gmail dot com 2008-06-14 18:16 ` danglin at gcc dot gnu dot org 2008-07-04 19:53 ` jsm28 at gcc dot gnu dot org [not found] <bug-35406-4@http.gcc.gnu.org/bugzilla/> 2015-02-12 0:28 ` jvdelisle 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=20080306183421.22070.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).