From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) by sourceware.org (Postfix) with ESMTPS id 317663858C27; Wed, 27 Oct 2021 20:46:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 317663858C27 Received: by mail-wr1-x432.google.com with SMTP id s14so3365295wrb.3; Wed, 27 Oct 2021 13:46:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=Z8PLrLdjkowauFFxwDbUsaZxysLbgnurc2Y/6+f8xdA=; b=aoI5miOecHZKJxQLGgDPlcveWODMe7YNAyJ6G1HZaCUbnEyhel95hQ+hoHjVNwjN6j sjfW0//SkFMXZmL6dFxMIMCm3fPQPehe26etmRVekPtoCSKx5Ee3SE3zFXILoqsNh5QR F0kHVz33wKlid67dMUXbVMgN+2cEVupr4SE5EaYtpz8AW4ok+BdE4gSx8qlBA4PA7jp/ aaM2921qHEMn6wgcXOarjAnrZirZMAHhNyabHRIlW9B7HRP1xXj6Xfp3pMw56Bj5lqeG 8kLQluKeMtFu+CZ+2vbRL8WdfW/X5dmsU4VWYyIwJ1R/loarso6cmg4iq8p2waDkMa7N S9Yw== X-Gm-Message-State: AOAM532Cvs3t3qeqN36csZVkvZh+2pvlsXlC661I4Dsf0REacJrSdjnn UT+83mHQvNWF3NgDirn5Q/o= X-Google-Smtp-Source: ABdhPJx4yaiSA/KEx4axlcbUAyn0QR1MBVpkHfSP4DOPmwwiCocBl6kcwL7WNmTVSWMtTenFQ5VrHw== X-Received: by 2002:adf:cc82:: with SMTP id p2mr1288614wrj.298.1635367603308; Wed, 27 Oct 2021 13:46:43 -0700 (PDT) Received: from nbbrfq (dynamic-2bq7di4u2lfl4qjka9-pd01.res.v6.highway.a1.net. [2001:871:227:33a8:f6a3:c58c:7641:e771]) by smtp.gmail.com with ESMTPSA id k15sm920027wrx.13.2021.10.27.13.46.42 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Oct 2021 13:46:43 -0700 (PDT) Date: Wed, 27 Oct 2021 22:46:38 +0200 From: Bernhard Reutner-Fischer To: Harald Anlauf via Fortran Cc: rep.dot.nop@gmail.com, Harald Anlauf , gcc-patches@gcc.gnu.org Subject: Re: [Patch, Fortran] PR 86935: Bad locus in ASSOCIATE statement Message-ID: <20211027224638.67766280@nbbrfq> In-Reply-To: References: <9F1BA124-0E74-496E-9AAC-53C86052CF5F@gmail.com> <20211027194058.2764dfdb@nbbrfq> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 27 Oct 2021 20:46:45 -0000 On Wed, 27 Oct 2021 21:44:52 +0200 Harald Anlauf via Fortran wrote: > Hi Bernhard, > > Am 27.10.21 um 19:40 schrieb Bernhard Reutner-Fischer via Fortran: > > AFAICS current trunk still has this issue. > > Any takers? > > thanks, > > can you create a PR tracking this issue? now https://gcc.gnu.org/PR102973 > > AFAICS PR86935 has been fixed for gcc-9+. Yes, it is a pre existing possible bug that caught my eye when i looked at that patch, so admittedly unrelated to PR86935. thanks,