public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [RFA/testsuite] Disable loop unrolling for gcc.dg/pr34263.c
@ 2009-04-23 15:20 Daniel Jacobowitz
  0 siblings, 0 replies; only message in thread
From: Daniel Jacobowitz @ 2009-04-23 15:20 UTC (permalink / raw)
  To: gcc-patches

I set flag_unroll_loops = 1 in my backend for a test.  This test
failed, because it is checking for a loop cleanup optimization - but
tree level complete loop unrolling will remove the loop before we get
here, so there is nothing to clean up.

Is this reasonable to commit?  I didn't try to handle --target_board
unix/-funroll-loops which will put the multilib option after the
testcase option; that's something we've been having increasing
difficulty with, but I'm frankly not brave enough to change it.
I'm sure there'd be all kinds of fallout.

-- 
Daniel Jacobowitz
CodeSourcery

2009-04-23  Daniel Jacobowitz  <dan@codesourcery.com>

	* testsuite/gcc.dg/pr34263.c: Add -fno-unroll-loops.

Index: gcc/testsuite/gcc.dg/pr34263.c
===================================================================
--- gcc/testsuite/gcc.dg/pr34263.c	(revision 243180)
+++ gcc/testsuite/gcc.dg/pr34263.c	(working copy)
@@ -1,5 +1,5 @@
 /* { dg-do run } */
-/* { dg-options "-O2 -fdump-tree-optimized" } */
+/* { dg-options "-O2 -fdump-tree-optimized -fno-unroll-loops" } */
 /* Same test as 990128-1.c.  */
 
 extern int printf (const char *,...);

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-04-23 15:18 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-04-23 15:20 [RFA/testsuite] Disable loop unrolling for gcc.dg/pr34263.c Daniel Jacobowitz

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).