https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88303
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Libgomp certainly does respect RUNTESTFLAGS, I use
make check-target-libgomp RUNTESTFLAGS=c.exp=atomic-2.c
and similar very often.
Isn't the problem that toplevel check-fortran depends on
check-target-libgomp-fortran which does:
check-target-libgomp-fortran:
$(MAKE) RUNTESTFLAGS="$(RUNTESTFLAGS) fortran.exp" check-target-libgomp
and thus checks all fortran?
I have no idea what to change it to support what you want though, I'd suggest
just do
make -C gcc check-gfortran RUNTESTFLAGS="dg.exp=pr88269.f90" if you want to
check something in the GCC testsuite, not use the toplevel check-fortran.
Because say for
make check-fortran RUNTESTFLAGS='--target_board=unix\{-m32,-m64\}'
you'd still want to add fortran.exp in there, but perhaps not add it if you
specify some particular *.exp with arguments.
