From: Nicolas Koenig <koenigni@student.ethz.ch>
To: "Dominique d'Humières" <dominiq@lps.ens.fr>
Cc: GCC-Fortran-ML <fortran@gcc.gnu.org>
Subject: Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements
Date: Thu, 01 Jun 2017 18:26:00 -0000 [thread overview]
Message-ID: <343d2681-1ba2-5345-cafe-5839c03a412b@student.ethz.ch> (raw)
In-Reply-To: <2E75B017-9A43-4734-BF38-8FA7A69962B8@lps.ens.fr>
Hello Dominique,
it appears the problem with this test case is that it fails because of
another bug (see PR80945
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80945), that is triggered
in this test case by the patch. What is normally done in such a case?
Should I add a check for this special case or just wait until the bug is
fixed?
Thanks for your patience & help!
Nicolas
On 06/01/2017 04:37 PM, Dominique d'Humières wrote:
>> Le 1 juin 2017 à 16:19, Dominique d'Humières <dominiq@lps.ens.fr> a écrit :
>>
>> I see
>>
>> FAIL: gfortran.dg/deferred_character_2.f90 -O1 execution test
>> FAIL: gfortran.dg/deferred_character_2.f90 -O2 execution test
>> FAIL: gfortran.dg/deferred_character_2.f90 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
>> FAIL: gfortran.dg/deferred_character_2.f90 -O3 -g execution test
>> FAIL: gfortran.dg/deferred_character_2.f90 -Os execution test
>>
>> Dominique
> Reduced test
>
> PROGRAM hello
>
> IMPLICIT NONE
>
> CHARACTER(LEN=:),DIMENSION(:),ALLOCATABLE :: array_lineas
> CHARACTER(LEN=:),DIMENSION(:),ALLOCATABLE :: array_copia
> character (3), dimension (2) :: array_fijo = ["abc","def"]
> character (100) :: buffer
> INTEGER :: largo , cant_lineas , i
>
> write (buffer, "(2a3)") array_fijo
>
> largo = LEN (array_fijo)
>
> cant_lineas = size (array_fijo, 1)
>
> ALLOCATE(CHARACTER(LEN=largo) :: array_lineas(cant_lineas))
>
> READ(buffer,"(2a3)") (array_lineas(i),i=1,cant_lineas)
>
> print *, array_lineas
> print *, array_fijo
> if (any (array_lineas .ne. array_fijo)) call abort
>
> END PROGRAM
>
> Dominique
>
next prev parent reply other threads:[~2017-06-01 18:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 15:49 Dominique d'Humières
2017-05-29 16:24 ` Nicolas Koenig
2017-05-29 16:51 ` Dominique d'Humières
2017-05-31 15:40 ` Bernhard Reutner-Fischer
2017-05-31 15:49 ` Dominique d'Humières
2017-05-31 19:03 ` Dominique d'Humières
2017-05-31 23:15 ` Nicolas Koenig
2017-06-01 9:31 ` Dominique d'Humières
2017-06-01 14:19 ` Dominique d'Humières
2017-06-01 14:37 ` Dominique d'Humières
2017-06-01 18:26 ` Nicolas Koenig [this message]
2017-06-03 13:48 ` Nicolas Koenig
2017-06-03 16:25 ` Jerry DeLisle
2017-06-03 18:12 ` Bernhard Reutner-Fischer
2017-06-05 20:39 ` Nicolas Koenig
2017-06-06 11:05 ` Markus Trippelsdorf
2017-06-07 15:13 ` Renlin Li
2017-11-02 8:25 ` [testsuite, committed] Fix scan pattern in gfortran.dg/implied_do_io_1.f90 Tom de Vries
-- strict thread matches above, loose matches on Subject: below --
2017-05-27 19:49 [Patch, fortran] PR35339 Optimize implied do loops in io statements Nicolas Koenig
2017-05-28 22:07 ` Jerry DeLisle
2017-05-28 23:32 ` Nicolas Koenig
2017-05-29 6:40 ` Thomas Koenig
2017-05-29 14:06 ` Thomas Koenig
2017-05-29 15:32 ` Jerry DeLisle
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=343d2681-1ba2-5345-cafe-5839c03a412b@student.ethz.ch \
--to=koenigni@student.ethz.ch \
--cc=dominiq@lps.ens.fr \
--cc=fortran@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).