From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3139 invoked by alias); 15 Jul 2011 14:04:32 -0000 Received: (qmail 3128 invoked by uid 22791); 15 Jul 2011 14:04:30 -0000 X-SWARE-Spam-Status: No, hits=-2.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 15 Jul 2011 14:04:16 +0000 From: "burnus at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/45170] [F2003] allocatable character lengths X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: burnus at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Fri, 15 Jul 2011 14:04:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-07/txt/msg01247.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45170 --- Comment #18 from Tobias Burnus 2011-07-15 14:02:45 UTC --- (In reply to comment #16) > Error: Variable 'length' cannot appear in the expression at (1) > That comes from the specification expression check. If one removes the check, it works, i.e. it is just a resolution (resolve.c) problem and not a code generation one. (In reply to comment #17) > subroutine hello (n,string) > character(:),allocatable,intent(out)::string > integer,intent(in)::n > string=helloworld(:n) That one seems to be a very subtle issue, depending on the modifications (e.g. allocate(character(len=)) instead of alloc on assignment), one might get the correct string length - or even the correct string. Looking at the (original) dump, the string length should be always correct, hence, I think we generate a slightly wrong tree. The next step would be to look at -fdump-tree-optimized and then work backwards.