From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30194 invoked by alias); 9 Jul 2005 11:52:14 -0000 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 Received: (qmail 30153 invoked by uid 48); 9 Jul 2005 11:52:07 -0000 Date: Sat, 09 Jul 2005 12:04:00 -0000 Message-ID: <20050709115207.30152.qmail@sourceware.org> From: "tobi at gcc dot gnu dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041015190149.18022.gruel@astro.ufl.edu> References: <20041015190149.18022.gruel@astro.ufl.edu> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug fortran/18022] problem with structure and calling a function X-Bugzilla-Reason: CC X-SW-Source: 2005-07/txt/msg01090.txt.bz2 List-Id: ------- Additional Comments From tobi at gcc dot gnu dot org 2005-07-09 11:52 ------- Oh, and there's a third option which is probably awkward and very pessimizing: instead of assuming REAL*4 sized objects in the array, the callee could read the size from the array desriptor, and skip fields accordingly. Of course, one would then still have to point to &z[0].y instead of &z[0] in the second call. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18022