This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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


> Thomas Koenig <Thomas.Koenig@online.de> wrote on Fri, 08 Dec 2006:
>
...
> WRT the rest of the discussion, I'd like to point out that -O3
> -ftree-vectorize currently ICEs on a few testcases (PR30087), which is

Does this patch fix the problem?:
http://gcc.gnu.org/ml/gcc/2006-12/msg00267.html


> why I haven't yet applied a patch.  Nevertheless, this makes it look
> like an important test.
>
> I don't think we should grow the list of options we cycle through,
> testsuite runtime is an issue, even if the gfortran testsuite is the
> fastest testsuite in gcc.  Anyway, things may look quite different
> with a separate testsuite for the library.
>
> The option list I have in my tree looks like this:
> { -O0 } { -O1 } { -O2 } \
> { -O2 -ftree-vectorize } \

To overcome the problem Andrew mentions here -
http://gcc.gnu.org/ml/gcc-patches/2006-12/msg00532.html,
you can look at how gcc.dg/vect/vect.exp computes which target options to
use with -ftree-vectorize.

dorit


> { -O2 -fomit-frame-pointer -finline-functions - fbounds-check } \
> { -O2 -fomit-frame-pointer -finline-functions -funroll-loops } \
> { -O3 -g } \
> { -Os }
>
> - Tobi
>
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]