This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][Cilkplus] Array notations as a Condition for If and switch statements
- From: Andi Kleen <andi at firstfloor dot org>
- To: "Iyer\, Balaji V" <balaji dot v dot iyer at intel dot com>
- Cc: "gcc-patches\ at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 21 Dec 2011 16:06:48 -0800
- Subject: Re: [PATCH][Cilkplus] Array notations as a Condition for If and switch statements
- References: <BF230D13CA30DD48930C31D409933000EE74@FMSMSX102.amr.corp.intel.com>
"Iyer, Balaji V" <balaji.v.iyer@intel.com> writes:
> new file mode 100644
> index 0000000..833379b
> --- /dev/null
> +++ b/gcc/testsuite/gcc.dg/cilk-plus/array_notation_tests/if_test.c
> @@ -0,0 +1,162 @@
> +#include <stdio.h>
> +
> +int main (int argc, char **argv)
> +{
> + int x = 3, y, z, array[10], array2[10], TwodArray[10][10], jj,kk,ll ;
> + int FourDArray[10][10][10][10];
> + int ii = 0;
> +
> + if (argc != 3)
> + {
> + fprintf(stderr, "Usage: %s 10 15\n", argv[0]);
Who actually calls the test case with these parameters?
Normally it should run by itself by adding the respective dejagnu
headers and return success/failure. The later also needs some more
self checking I suspect, not just outputting the result.
You want the test suite to fail when the cilk arrays break.
-Andi
--
ak@linux.intel.com -- Speaking for myself only