From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1362 invoked by alias); 30 Aug 2006 04:46:46 -0000 Received: (qmail 1350 invoked by uid 48); 30 Aug 2006 04:46:39 -0000 Date: Wed, 30 Aug 2006 04:46:00 -0000 Message-ID: <20060830044639.1349.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/28890] ICE on write In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pault at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-08/txt/msg02620.txt.bz2 List-Id: ------- Comment #2 from pault at gcc dot gnu dot org 2006-08-30 04:46 ------- (In reply to comment #1) > Confirmed: changing the substring reference to the unambiguous > write (*,*) i, charr(i:i) > gets rid of the problem. Apparently, vene though charr is scalar, the > reference is being interpreted as an array reference. > > Paul > Cooh! Not only was I full of bulls**t last night but had gone sydlexic too! charr(i:i) is, of course, no more unambiguous than charr(i), except, apparently, in the bowels of gfortran! In fact, using -fdump-parse-tree, I find that charr(i) is being taken as a character function reference. It must be easy enough to put paid to that... Paul -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28890