From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21903 invoked by alias); 5 Sep 2018 17:02:36 -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 21894 invoked by uid 89); 5 Sep 2018 17:02:36 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-11.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_1,GIT_PATCH_2,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=HTo:U*toon X-HELO: mail-oi0-f67.google.com Received: from mail-oi0-f67.google.com (HELO mail-oi0-f67.google.com) (209.85.218.67) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 05 Sep 2018 17:02:31 +0000 Received: by mail-oi0-f67.google.com with SMTP id 8-v6so15056285oip.0 for ; Wed, 05 Sep 2018 10:02:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FhYGeDCRHU7IRJYiXziZQCLAyw8/jN4/o1AClSv6y/U=; b=XbaRH+cVBACScVIbcr8rId0/hADX6oR5alSdg/hGoHOJ6W3gZ32O7nkyN4JWm1acRY SOrvec2huUN5OGGOpyGJ6/jvjtVIvPenGPXEQPR7YGNzyzmSUTAS4DiGV4CEG/pyTkKV 0KQUa3KX0HZHNuvPtCZ/QTIS31QMhhkhNtBDyugCNNBOpCepxY6UK1lIGF4Q7kmHb8Yv X6yUAL+3dTvDuD3iakdXki+w3u3j7eYdC2k7VCTWigXaaD51athepnPVs+kGn5iaqB// NCIT9jwTJK3MhTfXDbYqmz84icOUd453yEarpB9GWg00ARmgqy/gPicvcK4KNrRfUNi8 jTuA== MIME-Version: 1.0 References: <024e798b9539b765a1259cfc9cb2f1dc480b24ca.1536144068.git.ams@codesourcery.com> <7f5064c3-afc6-b7b5-cade-f03af5b86331@moene.org> In-Reply-To: <7f5064c3-afc6-b7b5-cade-f03af5b86331@moene.org> From: Bernhard Reutner-Fischer Date: Wed, 05 Sep 2018 17:02:00 -0000 Message-ID: Subject: Re: [PATCH 08/25] Fix co-array allocation To: toon@moene.org Cc: gfortran , ams@codesourcery.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2018-09/txt/msg00056.txt.bz2 On Wed, 5 Sep 2018 at 18:54, Toon Moene wrote: > > mhm, but why don't these use size_zero_node ? thanks, > > > -------- Forwarded Message -------- > Subject: [PATCH 08/25] Fix co-array allocation > Date: Wed, 5 Sep 2018 12:49:40 +0100 > From: ams@codesourcery.com > To: gcc-patches@gcc.gnu.org > > > The Fortran front-end has a bug in which it uses "int" values for "size_t" > parameters. I don't know why this isn't problem for all 64-bit > architectures, > but GCN ends up with the data in the wrong argument register and/or > stack slot, > and bad things happen. > > This patch corrects the issue by setting the correct type. > > 2018-09-05 Kwok Cheung Yeung > > gcc/fortran/ > * trans-expr.c (gfc_trans_structure_assign): Ensure that > integer_zero_node is of sizetype when used as the first > argument of a call to _gfortran_caf_register. > * trans-intrinsic.c (conv_intrinsic_event_query): Convert computed > index to a size_t type. > * trans-stmt.c (gfc_trans_event_post_wait): Likewise. > --- > gcc/fortran/trans-expr.c | 2 +- > gcc/fortran/trans-intrinsic.c | 3 ++- > gcc/fortran/trans-stmt.c | 3 ++- > 3 files changed, 5 insertions(+), 3 deletions(-) > >