From: Thomas Koenig <tkoenig@netcologne.de>
To: "fortran@gcc.gnu.org" <fortran@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [patch, Fortran, committed] Fixed test case
Date: Sun, 03 May 2015 18:17:00 -0000 [thread overview]
Message-ID: <5546663F.3080908@netcologne.de> (raw)
Hello world,
I have just committed the following patch as obvious after testing.
This fixes the regression from the incorrect code in the test case
of my lbound simplification patch.
Regards
Thomas
Index: gfortran.dg/bound_9.f90
===================================================================
--- gfortran.dg/bound_9.f90 (Revision 222661)
+++ gfortran.dg/bound_9.f90 (Arbeitskopie)
@@ -54,6 +54,7 @@
call foo(empty, a(2:0), n, m)
if (n .ne. 1 .or. m .ne. 1) call abort
allocate (x(0))
+ y => a(3:2)
call bar (x, y, n, m)
if (n .ne. 1 .or. m .ne. 1) call abort
2015-05-03 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/37131
* gfortran.dg/bound_9.f90: Add pointer assignment.
reply other threads:[~2015-05-03 18:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5546663F.3080908@netcologne.de \
--to=tkoenig@netcologne.de \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
/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).