[Patch, gcc, testsuite] Adjust optimization levels for some cases.

[Mike Stump]

On Oct 19, 2011, at 11:45 PM, Terry Guo wrote:
> These four cases check the amount of the desired instructions. At O2 level,
> some factors like loop unroll will increase the amount of them. This patch
> is proposing to adjust the optimization level to O1 (the minimal
> requirement) to avoid such impact. In this way, the cases are more robust.
> Regression test is performed on arm-none-eabi target. No regression found.
> Is it OK to trunk?

I've not seen any approval, rejection or review of this yet.  Absents objections from the arm folks or the optimization folks, Ok.  If someone thinks this is a bad idea, time to step forward.  :-)

> 2011-10-20  Terry Guo  <terry.guo@arm.com>
> 
>        * gcc.target/arm/wmul-1.c: Adjust optimization levels.
>        * gcc.target/arm/wmul-2.c: Ditto.
>        * gcc.target/arm/wmul-3.c: Ditto.
>        * gcc.target/arm/wmul-4.c: Ditto.
> 
> diff --git a/gcc/testsuite/gcc.target/arm/wmul-1.c
> b/gcc/testsuite/gcc.target/arm/wmul-1.c
> index 426c939..ddddd50 100644
> --- a/gcc/testsuite/gcc.target/arm/wmul-1.c
> +++ b/gcc/testsuite/gcc.target/arm/wmul-1.c

> -/* { dg-options "-O2" } */
> +/* { dg-options "-O1 -fexpensive-optimizations" } */