This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug testsuite/38791] FAIL: gcc.dg/graphite/block-3.c (test for excess errors)
- From: "sebpop at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Jan 2009 14:45:33 -0000
- Subject: [Bug testsuite/38791] FAIL: gcc.dg/graphite/block-3.c (test for excess errors)
- References: <bug-38791-12313@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #8 from sebpop at gmail dot com 2009-01-14 14:45 -------
Subject: Re: FAIL: gcc.dg/graphite/block-3.c (test for excess errors)
> Before closing this pr as fixed, I have a question: usually tests having
> -fdump-* in dg-options are doing some search of patterns in the dumped file,
> e.g. in gcc/testsuite/gcc.dg/pr35729.c
>
> /* { dg-options "-Os -fdump-rtl-loop2_invariant" } */
> ...
> /* { dg-final { scan-rtl-dump-times "Decided to move invariant" 0
> "loop2_invariant" } } */
>
> I noticed that gcc/testsuite/gcc.dg/graphite/block-3.c has only the cleaning
> dg-final, but no scan-* one(s). I don't see anything in
> gcc/testsuite/gcc.dg/graphite/graphite.exp that could supply it either.
> Is this the intended behavior or is there something missing in this test (and
> possibly other graphite ones)?
The test for loop blocking is missing in block-3.c. We will have to
clean up the graphite testsuite and making the tests more reliable,
but probably this will be done in GCC4.5.
Sebastian
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38791