From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 111542 invoked by alias); 1 Jun 2017 18:26:27 -0000 Mailing-List: contact fortran-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: fortran-owner@gcc.gnu.org Received: (qmail 111521 invoked by uid 89); 1 Jun 2017 18:26:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=0.5 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,LIKELY_SPAM_FROM,RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=H*M:cafe X-HELO: edge20.ethz.ch Received: from edge20.ethz.ch (HELO edge20.ethz.ch) (82.130.99.26) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 01 Jun 2017 18:26:20 +0000 Received: from CAS22.d.ethz.ch (172.31.51.112) by edge20.ethz.ch (82.130.99.26) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 1 Jun 2017 20:26:16 +0200 Received: from [192.168.0.227] (77.58.177.254) by mail.ethz.ch (172.31.51.112) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 1 Jun 2017 20:26:21 +0200 Subject: Re: [Patch, fortran] PR35339 Optimize implied do loops in io statements To: =?UTF-8?Q?Dominique_d'Humi=c3=a8res?= References: <92F638BD-768E-4C83-9BA9-0FACFC7F6C07@lps.ens.fr> <53722520-52ae-0fa7-d732-f30995c9f93a@student.ethz.ch> <638D5570-F9B9-4522-A123-CDC0B95D4227@lps.ens.fr> <84e2e0b8-26d2-bf0c-35ae-dd8f63a111fe@student.ethz.ch> <28B2EA4E-59C0-4E78-B04B-ECAD49EB614B@lps.ens.fr> <2E75B017-9A43-4734-BF38-8FA7A69962B8@lps.ens.fr> From: Nicolas Koenig CC: GCC-Fortran-ML Message-ID: <343d2681-1ba2-5345-cafe-5839c03a412b@student.ethz.ch> Date: Thu, 01 Jun 2017 18:26:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <2E75B017-9A43-4734-BF38-8FA7A69962B8@lps.ens.fr> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes X-SW-Source: 2017-06/txt/msg00003.txt.bz2 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 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 >