[gfortran, testsuite] Fix bounds checking for substrings, enable bounds chekcing in dg testsuite, assorted fixes

[Tobias Schlüter]

Tobias Schlüter <tobias.schlueter@physik.uni-muenchen.de> wrote on  
Sat, 25 Nov 2006:
> The list of options that we cycle through with this patch is:
>     set TORTURE_OPTIONS [list \
>         { -O0 } { -O1 } { -O2 } \
>         { -O2 -fomit-frame-pointer -finline-functions } \
>         { -O2 -fomit-frame-pointer -finline-functions -funroll-loops } \
>         { -O2 -fbounds-check } \
>         { -O2 -fno-repack-arrays } \
>         { -O3 -g } \
>         { -Os }]
> while previously, the dg testsuite would cycle through the following list
>         { -O0 } \
>         { -O1 } \
>         { -O2 } \
>         { -O3 -fomit-frame-pointer } \
>         { -O3 -fomit-frame-pointer -funroll-loops } \
>         { -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions } \
>         { -O3 -g } \
>         { -Os }
>
> This is a good time to speak up if you think that list is too long,
> your favorite option is missing, etc.  I'm open to suggestions how to
> shorten this list, as in its current incarnation the patch will grow
> the list of options by 12.5%

Since PR30003 is about to be fixed, I'd like to bring this question  
back to the front.  What options would we liek the testsuite to cycle  
through.  According to FX' suggestion, I replaced -fno-repack-arrays  
by -ftree-vectorize in my local tree.  Are you ok with cycling through  
one more option, or would you rather see somethign cropped from the  
list?

Cheers,
- Tobi

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.