From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32358 invoked by alias); 16 Mar 2008 15:56:19 -0000 Received: (qmail 31957 invoked by uid 48); 16 Mar 2008 15:55:37 -0000 Date: Sun, 16 Mar 2008 15:56:00 -0000 Message-ID: <20080316155537.31956.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/34714] ICE-on-invalid in gfc_conv_descriptor_dtype In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dfranke at gcc dot gnu dot org" 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: 2008-03/txt/msg01371.txt.bz2 ------- Comment #2 from dfranke at gcc dot gnu dot org 2008-03-16 15:55 ------- > function func2() > type(bar) func2 > allocate(func1%baz(1)) > end function In primary.c(match_variable), case FL_PROCEDURE, we here have a function that satisfies the first if-clause, but does not trigger the second. Hence, code-flow squirrels down to the handling of variables, instead of bailing out with an not-a-variable error. Btw, if func1 is defined with a RESULT variable instead, we produce the expected error ^^ -- dfranke at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dfranke at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2008-01-16 20:36:53 |2008-03-16 15:55:37 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34714