From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Cc: fortran@gcc.gnu.org
Subject: [PATCH] Fix gfortran.dg/pr51434.f90 testcase
Date: Thu, 03 May 2018 07:32:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.20.1805030931220.24704@zhemvz.fhfr.qr> (raw)
As noted in the bug the testcase is bogus. The following should
hopefully fix the observed runtime failures on powerpc and arm.
I've changed the bug to a FE accepts-invalid one.
Committed.
Richard.
2018-05-03 Richard Biener <rguenther@suse.de>
PR testsuite/85579
* fortran.dg/pr51434.f90: Truncate transfer argument.
Index: gcc/testsuite/gfortran.dg/pr51434.f90
===================================================================
--- gcc/testsuite/gfortran.dg/pr51434.f90 (revision 259879)
+++ gcc/testsuite/gfortran.dg/pr51434.f90 (working copy)
@@ -6,7 +6,7 @@ module foo
character(len=1), parameter :: s(n) = 'a'
type :: a
integer :: m = n
- character(len=1):: t(n) = transfer('abcde ', s)
+ character(len=1):: t(n) = transfer('abcde', s)
end type a
end module foo
reply other threads:[~2018-05-03 7:32 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=alpine.LSU.2.20.1805030931220.24704@zhemvz.fhfr.qr \
--to=rguenther@suse.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).