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 <anl...@gmx.de> 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() 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 course, for final testing > > I do a full regression test. > > This is documented, and this I know, too, and I use it. However, > it does not stop the torture testing with cycling over options. > > When I played with the parsing of inquiry references, I expected > to hit parsing and/or resolution issues in other tests whose > name I could guess at best. The turnaround time for working > on such basic things is just too high. > > When searching the internet, there is a mentioning of previously > existing environment variables (e.g. TORTURE_OPTIONS or > DG_TORTURE_OPTIONS), but they either do not work - or work > in a way that I do not see. > > Jakub recently hacked something that prevents cycling if an > explicit -Ox appears in dg-options. I thought that a lightweight > checking feature could exploit a similar trick. > > Cheers, > Harald > >
