On Fri, Apr 10, 2020 at 8:14 AM Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: > > Hi Fritz, [...] > one new testcases comes up as UNRESOLVED everywhere: > > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-not > original "volatile.*?ivar_noasync" > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?ccvar_async" 1 > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?darrvar_async" 1 > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?dvar_async" 1 > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?ivar_async" 1 > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?lvar_async" 1 > +UNRESOLVED: gfortran.dg/asynchronous_5.f03 -O scan-tree-dump-times > original "volatile.*?rvar_async" 1 > > gfortran.dg/asynchronous_5.f03 -O : dump file does not exist > > It has several scan-tree-dump* checks, but no corresponding > -fdump-tree-* option. Please fix (and make sure not to look only for > FAILs during regtesting in the future). > > Rainer
Ah! My mistake... I will fix and look for this in the future. Fritz
