From: Thomas Schwinge <thomas@codesourcery.com>
To: Jakub Jelinek <jakub@redhat.com>, Tobias Burnus <burnus@net-b.de>,
gcc-patches <gcc-patches@gcc.gnu.org>,
gfortran <fortran@gcc.gnu.org>, FX <fxcoudert@gmail.com>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [Patch, Fortran + Testsuite] Fix coarray handling in modules
Date: Thu, 28 Feb 2019 17:19:00 -0000 [thread overview]
Message-ID: <87k1hjonh3.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <54A680CA.90509@net-b.de>
[-- Attachment #1.1: Type: text/plain, Size: 2055 bytes --]
Hi!
On Fri, 02 Jan 2015 12:28:10 +0100, Tobias Burnus <burnus@net-b.de> wrote:
> [...]
>
> I additionally propagated the dg-compile-aux-modules support to caf.dg
That got committed in r219143:
> --- a/gcc/testsuite/gfortran.dg/coarray/caf.exp
> +++ b/gcc/testsuite/gfortran.dg/coarray/caf.exp
> @@ -43,6 +43,21 @@ global DG_TORTURE_OPTIONS torture_with_loops
> torture-init
> set-torture-options $DG_TORTURE_OPTIONS
>
> +global gfortran_test_path
> +global gfortran_aux_module_flags
> +set gfortran_test_path $srcdir/$subdir
> +set gfortran_aux_module_flags $DEFAULT_FFLAGS
> +proc dg-compile-aux-modules { args } {
> + global gfortran_test_path
> + global gfortran_aux_module_flags
> + if { [llength $args] != 2 } {
> + error "dg-set-target-env-var: needs one argument"
> + return
> + }
> + dg-test $gfortran_test_path/[lindex $args 1] "" $gfortran_aux_module_flags
> + # cleanup-modules isn't intentionally invoked here.
> +}
I just noticed that this copy is missing Jakub's r215293 changes that he
had applied a few months *earlier* to the master copy of
'dg-compile-aux-modules', in 'gcc/testsuite/gfortran.dg/dg.exp', see
attached, and/or
<http://mid.mail-archive.com/20140916093700.GW17454@tucnak.redhat.com>.
I can't easily test it with the affected DejaGnu version 1.4.4 (which is
still the minimum version required now), but it tests fine with DejaGnu
1.5, and seems straight-forward, so I propose I commit "as obvious" these
changes to the 'gcc/testsuite/gfortran.dg/coarray/caf.exp' copy, too?
(It's exactly these changes missing to make the two copies identical.)
The other copy, created later, in
'gcc/testsuite/gcc.target/powerpc/ppc-fortran/ppc-fortran.exp' already
does exactly match the master copy.
And then, of course, we really should unify all 'dg-compile-aux-modules'
copies into one shared file. (But it's not completely straight-forward,
because of the handling of 'gfortran_test_path', and
'gfortran_aux_module_flags'.)
Grüße
Thomas
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-PR-fortran-56408.patch --]
[-- Type: text/x-diff, Size: 1892 bytes --]
From 6278a9a2afb7d4d730c585f93d2bd435ed63f963 Mon Sep 17 00:00:00 2001
From: jakub <jakub@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Tue, 16 Sep 2014 09:35:00 +0000
Subject: [PATCH] PR fortran/56408 * gfortran.dg/dg.exp
(dg-compile-aux-modules): Workaround missing nexted dg-test call support in
dejaGNU 1.4.4.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@215293 138bc75d-0d04-0410-961f-82ee72b054a4
---
gcc/testsuite/ChangeLog | 6 ++++++
gcc/testsuite/gfortran.dg/dg.exp | 12 +++++++++++-
2 files changed, 17 insertions(+), 1 deletion(-)
diff --git a/gcc/testsuite/ChangeLog b/gcc/testsuite/ChangeLog
index fdb706a8d8dd..4d3c96beee2c 100644
--- a/gcc/testsuite/ChangeLog
+++ b/gcc/testsuite/ChangeLog
@@ -1,3 +1,9 @@
+2014-09-16 Jakub Jelinek <jakub@redhat.com>
+
+ PR fortran/56408
+ * gfortran.dg/dg.exp (dg-compile-aux-modules): Workaround
+ missing nexted dg-test call support in dejaGNU 1.4.4.
+
2014-09-15 Andi Kleen <ak@linux.intel.com>
* gcc.dg/pg-override.c: New test.
diff --git a/gcc/testsuite/gfortran.dg/dg.exp b/gcc/testsuite/gfortran.dg/dg.exp
index e8c39231db00..6bd69e6c88d0 100644
--- a/gcc/testsuite/gfortran.dg/dg.exp
+++ b/gcc/testsuite/gfortran.dg/dg.exp
@@ -39,8 +39,18 @@ proc dg-compile-aux-modules { args } {
error "dg-set-target-env-var: needs one argument"
return
}
+
+ set level [info level]
+ if { [info procs dg-save-unknown] != [list] } {
+ rename dg-save-unknown dg-save-unknown-level-$level
+ }
+
dg-test $gfortran_test_path/[lindex $args 1] "" $gfortran_aux_module_flags
- # cleanup-modules isn't intentionally invoked here.
+ # cleanup-modules is intentionally not invoked here.
+
+ if { [info procs dg-save-unknown-level-$level] != [list] } {
+ rename dg-save-unknown-level-$level dg-save-unknown
+ }
}
# Main loop.
--
2.17.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
next prev parent reply other threads:[~2019-02-28 17:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-02 11:28 Tobias Burnus
2015-01-02 13:14 ` FX
2015-01-02 20:47 ` Mike Stump
2019-02-28 17:19 ` Thomas Schwinge [this message]
2019-03-21 19:34 ` Thomas Schwinge
2015-01-03 10:22 Dominique Dhumieres
2015-01-03 20:50 ` Tobias Burnus
2015-01-03 21:48 ` Dominique d'Humières
2015-01-03 22:30 ` Tobias Burnus
2015-01-03 23:04 ` Dominique d'Humières
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=87k1hjonh3.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=burnus@net-b.de \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mikestump@comcast.net \
/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).