>>> FAIL: gfortran.dg/f2003_inquire_1.f03 -O1 execution test
>
> This seems to be a bug in the test suite. It tries to find out whether an id
> is pending that is never initialized.
>
>>> FAIL: gfortran.dg/f2003_io_1.f03 -O*
>
> And another bug in the test suite. This time the wait after the read is
> missing.
Do you have any fix for them ?
> asynchronous_7.f90 is a test for an error, but dg-shouldfail is not working
> in libgomp. Dominique is looking into this.
I have this in my working tree
! { dg-do run }
program main
integer :: i
open (10,file="tst.dat")
write (10,'(A4)') 'asdf'
close(10)
i = 234
open(10,file="tst.dat", asynchronous="yes")
read (10,'(I4)',asynchronous="yes") i
wait(10)
end program main
! { dg-output "Fortran runtime error: Bad value during integer read" }
! { dg-final { remote_file build delete "tst.dat" } }
>
>> Besides, I see
>> +FAIL: libgomp.fortran/asynchronous_6.f90 -O1 execution test
>> STOP 2
>> 32-bit i386 only.
>
> I have trouble replicating this bug even with -m32. Could you get some more
> debugging info for the test on your machine?
I have copied the asynchronous tests from libgomp.fortran to gfortran.dg and
ran both
make -k check-gfortran RUNTESTFLAGS="dg.exp=asynchronous_*
--target_board=unix'{-m32,-m64}’"
in gcc and
make -k check RUNTESTFLAGS="fortran.exp=asynchronous_*.f90
--target_board=unix'{-m32,-m64}’"
in x86_64-apple-darwin17.6.0/libgomp/testsuite 10 times and I see ~10 failures
in each cases (mostly STOP 2, but also STOP 4). I some cases I had to kill the
process.
Note that these tests should probably protected by something such as
! { dg-require-effective-target pthread }
or
! { dg-require-effective-target tls }
Dominique
