From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 112871 invoked by alias); 20 Mar 2018 22:49:53 -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 112037 invoked by uid 89); 20 Mar 2018 22:49:52 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=H*c:alternative, H*c:HHHHHHHH, H*c:HHHH X-HELO: mail-pg0-f47.google.com Received: from mail-pg0-f47.google.com (HELO mail-pg0-f47.google.com) (74.125.83.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 20 Mar 2018 22:49:51 +0000 Received: by mail-pg0-f47.google.com with SMTP id m24so1224633pgv.8 for ; Tue, 20 Mar 2018 15:49:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=z1fC5/DktJwbE6U+VneXKitQ7es8NfEnYSjEQrnUiEs=; b=P/QR0wuFl/l6Ozt3rv9fSAznH6fdG3++nnDLkX6x0W4H5kCoufGRkvZrv1ge2UcLD5 ZBVbtHaEFaiTVmySFT/KKV/mMDxC2IGtuMhWkF2my6O1YQb4+6pXYwA+ITnn0bQOJIzy T8MAc5/uAow0TpIR+Cj+BCpoTkQSRYpqnQ2Hs/37ghPmsuYfqFTI5gXZRVX1qaqjc5Nr 62ODw2spxtKtGPibk5Tp752NBg1iudiGaumTXKpfGHv9sGFRxaBAsPQ5cjcJM1jz/zTc em2CcPviB/yvVl0Gz5fxPXmpbdaOVNVAyhrJvixs5CQbpwSHv3+YExe2DxwPJceoY0Ka 4R6w== X-Gm-Message-State: AElRT7G9UcTUGjcrFVP0mIK1MN2aJjZVhhwo/odmAizvxYsR3hQ1Tzxv 207Ee7ShPX38C7BAllDvytMa085x X-Google-Smtp-Source: AG47ELvmXhqwB3Xk7jcobViUtM7D6yiLztgjAWsqaV98Z4Q7LIg08VHvO10aZx/zzO/1zqFHr8hmvQ== X-Received: by 10.101.98.205 with SMTP id m13mr13240546pgv.100.1521586189197; Tue, 20 Mar 2018 15:49:49 -0700 (PDT) Received: from localhost.mail ([50.233.164.226]) by smtp.gmail.com with ESMTPSA id y6sm4961788pfg.71.2018.03.20.15.49.47 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Mar 2018 15:49:48 -0700 (PDT) Date: Tue, 20 Mar 2018 22:49:00 -0000 From: Damian Rouson To: gfortran , =?utf-8?Q?Vladim=C3=ADr_Fuka?= Message-ID: In-Reply-To: References: Subject: Re: Bug 84894 - [F2018] provide iso_fortran_binding.h MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2018-03/txt/msg00107.txt.bz2 On March 20, 2018 at 7:14:31 AM, Vladim=C3=ADr Fuka (vladimir.fuka@gmail.co= m) wrote: > In my last fortran-dev install I see a file=C2=A0 > intall_dir/lib/gcc/x86_64-apple-darwin15.6.0/7.0.0/include/ISO_Fortran_bi= nding.h=C2=A0 > I am attaching. Could you please check=C2=A0 Dominique,=C2=A0 is the header compatible with the current array descriptor for GCC8?=C2=A0 I assume it=E2=80=99s not compatible because the header file was written ye= ars ago and the new descriptors were communities on 25 January 2018. =C2=A0= First, I=E2=80=99m hoping to just check whether MPICH will recognize it and= progress to the next step so that I can ensure whether there is also anoth= er issue that crops up. =C2=A0Even if MPICH accepts the file and attempts t= o use it, I=E2=80=99m sure there will be many test failures because of the = descriptor change and other forms of bit rot. Damian