> Gesendet: Mittwoch, 4. Juni 2025 um 20:37
> Von: "Jerry D"
> An: "Mikael Morin" , "Harald Anlauf" ,
> fortran@gcc.gnu.org
> Betreff: Re: Execution time for gfortran regression testing
>
> On 6/3/25 3:02 AM, Mikael Morin wrote:
> > The
On 6/3/25 3:02 AM, Mikael Morin wrote:
Le 30/05/2025 à 22:28, Harald Anlauf a écrit :
When I'm working on a particular area of gfortran, I tend
to use RUNTESTFLAGS to limit what is tested. For example,
I just fixed SPREAD() for scalar source and ncopies < 1.
I do
% cd obj
% gmake
% cd gcc
% gm
Le 30/05/2025 à 22:28, Harald Anlauf a écrit :
When I'm working on a particular area of gfortran, I tend
to use RUNTESTFLAGS to limit what is tested. For example,
I just fixed SPREAD() for scalar source and ncopies < 1.
I do
% cd obj
% gmake
% cd gcc
% gmake check-fortran RUNTESTFLAGS="dg.exp=s
You could possibly modify the dg.exp file. These are basically scripts.
It's a bit of a pain.
On Fri, May 30, 2025, 1:29 PM Harald Anlauf wrote:
> > When I'm working on a particular area of gfortran, I tend
> > to use RUNTESTFLAGS to limit what is tested. For example,
> > I just fixed SPREAD()
When I'm working on a particular area of gfortran, I tend
to use RUNTESTFLAGS to limit what is tested. For example,
I just fixed SPREAD() for scalar source and ncopies < 1.
I do
% cd obj
% gmake
% cd gcc
% gmake check-fortran RUNTESTFLAGS="dg.exp=spread\*.f90"
This only runs 63 tests. Of cours
On Fri, May 30, 2025 at 09:03:27PM +0200, Harald Anlauf wrote:
>
> the time needed for running the gfortran testsuite has increased so
> much that I am looking for options to get this down to something
> that is more bearable when working on a Fortran-only patch.
>
> I am already building with --
Dear all,
the time needed for running the gfortran testsuite has increased so
much that I am looking for options to get this down to something
that is more bearable when working on a Fortran-only patch.
I am already building with --disable-bootstrap, as I cannot afford
a full bootstrap. It is a
