From: Fritz Reese <fritzoreese@gmail.com>
To: Rainer Orth <ro@cebitec.uni-bielefeld.de>
Cc: Fritz Reese via Gcc-patches <gcc-patches@gcc.gnu.org>,
Tobias Burnus <tobias@codesourcery.com>,
fortran <fortran@gcc.gnu.org>
Subject: Re: [PATCH, Fortran] -- PR fortran/87923 -- fix ICE when resolving I/O tags and simplify io.c
Date: Fri, 10 Apr 2020 11:12:43 -0400 [thread overview]
Message-ID: <CAE4aFAnHCVk7dGw-wE78fa1byTtiMe4jdweUg==kwiY4r0HBAw@mail.gmail.com> (raw)
In-Reply-To: <ydd4ktro7vx.fsf@CeBiTec.Uni-Bielefeld.DE>
On Fri, Apr 10, 2020 at 8:14 AM Rainer Orth <ro@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
prev parent reply other threads:[~2020-04-10 15:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 17:25 Fritz Reese
2020-04-09 9:20 ` Tobias Burnus
2020-04-09 20:59 ` Fritz Reese
2020-04-10 12:14 ` Rainer Orth
2020-04-10 15:12 ` Fritz Reese [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4aFAnHCVk7dGw-wE78fa1byTtiMe4jdweUg==kwiY4r0HBAw@mail.gmail.com' \
--to=fritzoreese@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=tobias@codesourcery.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).