This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] Fix PR37686: Correct how lambda gets the loop index for the matrix representation of array accesses
- From: Jakub Jelinek <jakub at redhat dot com>
- To: Sebastian Pop <sebpop at gmail dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, Daniel Berlin <dberlin at dberlin dot org>
- Date: Sat, 4 Oct 2008 01:39:55 +0200
- Subject: Re: [patch] Fix PR37686: Correct how lambda gets the loop index for the matrix representation of array accesses
- References: <cb9d34b20810031521i14349535s20d1ec617e5b1102@mail.gmail.com>
- Reply-to: Jakub Jelinek <jakub at redhat dot com>
On Fri, Oct 03, 2008 at 05:21:45PM -0500, Sebastian Pop wrote:
> --- testsuite/gcc.dg/tree-ssa/pr37686.c (revision 0)
> +++ testsuite/gcc.dg/tree-ssa/pr37686.c (revision 0)
> @@ -0,0 +1,48 @@
> +/* { dg-do compile { target powerpc*-*-* } } */
> +/* { dg-options "-mcpu=power4 -m64 -mtune=cell -O3 -ftree-loop-linear --param ggc-min-expand=0 --param ggc-min-heapsize=0 -funroll-loops -fpreprocessed" } */
Either the testcase is ppc specific and then it should go under
gcc.target/powerpc/, or it is not and then you just should compile
it everywhere, perhaps with special flags on ppc and just use
-O3 -ftree-loop-linear -funroll-loops on all the other arches.
My preference would be the latter in this case.
Jakub