This is the mail archive of the 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


Andrew Pinski wrote:
> Remember the gfortran testsuite is a testsuite for both the front-end
> and the back-end and all parts inbetween. 
> Here is what I would use (and no this is not too long and gfortran
> testsuite is shorter to run than even the libstdc++ testsuite):
> -O0
> -O1
> -O2
> -Os
> -O3 -fomit-frame-pointer
> -O3 -fomit-frame-pointer -funroll-loops
> -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions
> -O3 -g
> -O2 -fbounds-check
> -O2 -fno-repack-arrays
> Yes there are 10 of them but remember the testsuite is for both the
> front-end usage and the back-end usage.  I might remove the
> unroll-all-loops one but I know gfortran usages are more likely to use
> that than normal GCC users.
I like those, but I miss two: (a) -ftree-vectorize [suggested by FX] and
(b) -fbounds-check [initial patch by Tobias S., see subject].  (Side
note: I really miss the possibility to run tests in parallel.)

For -fbounds-check I actually favour some combination with -O since my
feeling is that this increases the chance of an ICE.
(Actually, I also like to run programs with checks and high optimization
to find potential programming errors without having to wait too long.)


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