public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Tobias Burnus <burnus@net-b.de>
To: Dominique Dhumieres <dominiq@lps.ens.fr>
Cc: fortran@gcc.gnu.org, gcc-patches@gcc.gnu.org,
	hjl.tools@gmail.com,  mikael.morin@sfr.fr
Subject: Re: *PING* / Re: [Patch, Fortran] Finalize nonallocatables with INTENT(out)
Date: Wed, 12 Jun 2013 13:18:00 -0000	[thread overview]
Message-ID: <51B87535.7030606@net-b.de> (raw)
In-Reply-To: <20130609104620.A97DF3BE1B@mailhost.lps.ens.fr>

[-- Attachment #1: Type: text/plain, Size: 482 bytes --]

Thanks Dominique and Andreas for reporting this issue.

Dominique Dhumieres wrote:
> The test gfortran.dg/finalize_10.f90 fails in 32 bit mode [...]
> The following patch fixes it
> [...]
>   
> I have tried to weaken the test by not using any target and using a regexp
> of the kind "(int|long)", but I did not succeeded.

Seemingly, dg-tree-dump-times does not work with regular expressions. I 
have replaces it by dg-tree-dump + regular expression.

Committed as 200003.

Tobias

[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 1405 bytes --]

Index: gcc/testsuite/ChangeLog
===================================================================
--- gcc/testsuite/ChangeLog	(Revision 200002)
+++ gcc/testsuite/ChangeLog	(Arbeitskopie)
@@ -1,3 +1,8 @@
+2013-06-12  Tobias Burnus  <burnus@net-b.de>
+	    Dominique d'Humieres  <dominiq@lps.ens.fr>
+
+	* gfortran.dg/finalize_10.f90: Update dg-dump.
+
 2013-06-12  Jakub Jelinek  <jakub@redhat.com>
 
 	PR target/56564
Index: gcc/testsuite/gfortran.dg/finalize_10.f90
===================================================================
--- gcc/testsuite/gfortran.dg/finalize_10.f90	(Revision 200002)
+++ gcc/testsuite/gfortran.dg/finalize_10.f90	(Arbeitskopie)
@@ -26,7 +26,7 @@
 
 ! Finalize CLASS + set default init
 ! { dg-final { scan-tree-dump-times "y->_vptr->_final \\(&desc.\[0-9\]+, y->_vptr->_size, 0\\);" 1 "original" } }
-! { dg-final { scan-tree-dump-times "__builtin_memcpy \\(\\(void .\\) y->_data, \\(void .\\) y->_vptr->_def_init, \\(unsigned long\\) y->_vptr->_size\\);" 1 "original" } }
+! { dg-final { scan-tree-dump       "__builtin_memcpy \\(\\(void .\\) y->_data, \\(void .\\) y->_vptr->_def_init, \\(unsigned (long|int)\\) y->_vptr->_size\\);" "original" } }
 ! { dg-final { scan-tree-dump-times "x->_vptr->_final \\(&x->_data, x->_vptr->_size, 0\\);" 1 "original" } }
 ! { dg-final { scan-tree-dump-times "x->_vptr->_copy \\(x->_vptr->_def_init, &x->_data\\);" 1 "original" } }
 

  reply	other threads:[~2013-06-12 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-09 10:46 Dominique Dhumieres
2013-06-12 13:18 ` Tobias Burnus [this message]
2013-06-12 13:29   ` Tobias Burnus
  -- strict thread matches above, loose matches on Subject: below --
2013-05-31 16:39 Tobias Burnus
2013-06-06  8:35 ` *PING* / " Tobias Burnus
2013-06-08 11:11   ` Mikael Morin
2013-06-08 12:40     ` Tobias Burnus
2013-06-09 11:35   ` Andreas Schwab

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=51B87535.7030606@net-b.de \
    --to=burnus@net-b.de \
    --cc=dominiq@lps.ens.fr \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --cc=mikael.morin@sfr.fr \
    /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).