From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) by sourceware.org (Postfix) with ESMTPS id F0C813857C7E for ; Tue, 25 Jan 2022 15:13:56 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org F0C813857C7E Received: by mail-wr1-x429.google.com with SMTP id e8so18711872wrc.0 for ; Tue, 25 Jan 2022 07:13:56 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZeQ12ABuD7VAcKSwDghIve6IPMtM6OkKeE4E3YtFIBQ=; b=nJDpqbZY3t1zKzyoxCllGeYVywcKEXqlg8+V2UZfQ4A6K5mHsaINq6U7rPyeAgzE1l 7dk/OZ4dtscX6lCWwxBd6oCryIUXIqofZ6NFiR/73Ut2w9QRmrxCjf6QiJNmSPkPY/Gj ETBStwjpwoifIyNROtt0Si/P+nAzHFJU5CUH+IUxMJF6uXNAA72eDPFzQzT46evfrjdj BxbQ3JTo2qHY4qNKwUa3NdrzcV0kWLUCtQuD7hVDuPT3I6xO4BwjzW707JzKgdJBKqO/ kqpDctJjtE5DLGYZ+mpMbdvZq9a2BWe6BCmkkDO2Y/FAA1T5yuBPWh51evU+AqsRVl2C 7QLw== X-Gm-Message-State: AOAM533Wh7UIuEIRnzXX6/IoUFdAUSmgdTQmf/PGtj9BYZCGevCiLOXm hmZ7LkAMM0EniIAAvV2XXbM= X-Google-Smtp-Source: ABdhPJxiFOkMO6+1fP//TfaS8sMzcGC63qAjW08CDIWLOnYzjHO9dSsXMDXuzV+8N5SOPdfrv3a54g== X-Received: by 2002:a5d:64ad:: with SMTP id m13mr7283233wrp.653.1643123635349; Tue, 25 Jan 2022 07:13:55 -0800 (PST) Received: from smtpclient.apple (chp127.enscp.fr. [193.51.253.127]) by smtp.gmail.com with ESMTPSA id h18sm2280241wro.9.2022.01.25.07.13.54 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 25 Jan 2022 07:13:54 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.40.0.1.81\)) Subject: Re: powerpc64le real(kind=16) and IEEE_{ARITHMETIC,EXCEPTIONS} modules From: FX In-Reply-To: Date: Tue, 25 Jan 2022 16:13:53 +0100 Cc: Jakub Jelinek , Thomas Koenig , fortran@gcc.gnu.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <20220125114427.GH2646553@tucnak> To: Tobias Burnus X-Mailer: Apple Mail (2.3693.40.0.1.81) X-Spam-Status: No, score=-1.8 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, 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: fortran@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Fortran mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jan 2022 15:13:59 -0000 > Thus, more functions could be handled in the compiler itself. > (Likewise for INTMOD_IEEE_EXCEPTIONS, not that I know whether > that has any relevant functions.) In theory, there is no reason why we need an explicit .mod file in the = library for any of the three IEEE modules. They would probably be better = treated as compiler intrinsics in the front-end itself, in fact, like = all other intrinsics. It would also be easier to adjust for generic = forms, and provide better diagnostics for mismatching arguments, etc. = This seems to be the way to go, as the next standard versions have added = even more intrinsics, some of which really shouldn=E2=80=99t be function = calls (comparison, ordering, etc). The reason those modules are not fully implemented in the front-end is = simple: I didn=E2=80=99t know how to implement them directly in the = front-end, and I am not entirely sure we have the appropriate stuff for = that. ISO_FORTRAN_ENV is implemented in the front-end, but its members = are simpler, really. In a way, you can see this as a call for help: if someone = front-end-savvy has ideas how to do this, we could partner up ;) FX=