Hi Tobias, thanks for these tips - this should come in handy indeed.
One thing though: when I tried to run my freshly built gfortran compiler on one of the test programs, I got the message that it could not find the file libgfortran.spec. Is there some environment variable that muist be set? Regards, Arjen Op ma 23 aug. 2021 om 21:36 schreef Tobias Burnus <bur...@net-b.de>: > Hi Arjen, > > On 23.08.21 20:59, Arjen Markus via Fortran wrote: > > as promised, here is an overview of the unexpectedly failing tests. I got > > these after applying the patches by Steve Kargl for bug ID 101951 and > > 101967. The platform I used to build it is Cygwin on WIndows 10. > > > > FAIL: gfortran.dg/analyzer/pr96949.f90 -O (internal compiler error) > > FAIL: gfortran.dg/analyzer/pr96949.f90 -O (test for excess errors) > > I recommend: https://gcc.gnu.org/pipermail/gcc-testresults/current – it > shows what others are getting. > > In particular, it helps: to ensure to look at the right branch (12.0 > mainline), to look at x86-64 Linux (as others tend to have some > additional issues) — and to make sure that that build actual does test > Fortran. > > But the simplest test is to undo your patches - recompile GCC and then > run (in the build directory): > > cd gcc; make check-fortran RUNTESTFLAGS="analyzer.exp=pr96949.f90" > > If the error still occurs, it is probably unrelated to the patch; if it > is gone, the patch probably caused it. > > I also do note that many analyzer commits have been committed today, > hence, it is a moving target. (It does work for me – with the current > checkout. But this does not tell anything about when you did your tests, > given that several commits were done this evening.) > > Tobias > >
