From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.smtpout.orange.fr (smtp-24.smtpout.orange.fr [80.12.242.24]) by sourceware.org (Postfix) with ESMTPS id D44CA3858286 for ; Sun, 11 Sep 2022 09:49:23 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D44CA3858286 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=orange.fr Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=orange.fr Received: from [192.168.1.17] ([86.215.174.255]) by smtp.orange.fr with ESMTPA id XJaVoV5UAUoLVXJabo5WrE; Sun, 11 Sep 2022 11:49:22 +0200 X-ME-Helo: [192.168.1.17] X-ME-Auth: bW9yaW4tbWlrYWVsQG9yYW5nZS5mcg== X-ME-Date: Sun, 11 Sep 2022 11:49:22 +0200 X-ME-IP: 86.215.174.255 Message-ID: <041d1f6b-9812-e1e3-dbd7-0416888804bc@orange.fr> Date: Sun, 11 Sep 2022 11:49:15 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.1 Subject: Re: [PATCH] Fortran: Add IEEE_SIGNBIT and IEEE_FMA functions To: FX , Thomas Koenig Cc: gcc-patches@gcc.gnu.org, FX via Fortran References: <7A9A82FB-3144-406C-A4E5-87F8EAC72044@gmail.com> <80F2E884-677E-4761-875A-082D853F913B@gmail.com> <5CFF18E6-7A7D-4042-A6E4-F170633CFA8F@gmail.com> <4A798A7C-1D75-41D2-8E09-192BDA810738@gmail.com> Content-Language: en-US From: Mikael Morin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-5.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,JMQ_SPF_NEUTRAL,KAM_DMARC_STATUS,NICE_REPLY_A,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Le 10/09/2022 à 12:14, FX via Fortran a écrit : > If you have a solution for the standards checking, I’ll add it. > As a first step, one could check the use rename lists; what's done for iso_fortran_env can be used as an example. To diagnose the other usages, the check could be put in resolve_symbol but it would diagnose it even if not used, so one can add a check on attr.referenced (I hope it can be relied upon). Another possibility is mimicking or modifying gfc_resolve_intrinsic, which already does a similar job for intrinsic procedures. I hope this helps.