From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.anongoth.pl (mail.anongoth.pl [46.248.190.61]) by sourceware.org (Postfix) with ESMTPS id 2F1DA3857829; Thu, 28 Apr 2022 17:09:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 2F1DA3857829 Received: from anongoth.pl (unknown [192.168.1.15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: pkubaj@anongoth.pl) by mail.anongoth.pl (Postfix) with ESMTPSA id 2F1CD19FB87; Thu, 28 Apr 2022 19:09:41 +0200 (CEST) Date: Thu, 28 Apr 2022 19:09:40 +0200 From: Piotr Kubaj To: FX Cc: gcc-patches@gcc.gnu.org, Fortran List , segher@kernel.crashing.org Subject: Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd Message-ID: References: <2E9BFB96-6979-4DB5-8029-1F89C30B242B@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ozKHMlGTKWz7p9Gt" Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, 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: Thu, 28 Apr 2022 17:09:47 -0000 --ozKHMlGTKWz7p9Gt Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Given that 12 has been branched off, is it OK now to commit this patch? On 22-04-14 16:09:35, Piotr Kubaj wrote: > On 22-04-14 09:05:17, FX wrote: > > Hi, > >=20 > > > can you check the following patch? > >=20 > > Why restrict it to powerpc-freebsd only, and not all freebsd? Do they d= iffer? > amd64 and i386 on all systems use a different setting and are not affecte= d. > For FreeBSD-supported architectures that are not amd64, i386 or powerpc*,= there are also armv6, armv7, aarch64, riscv64 and riscv64sf. >=20 > However, GCC is currently not ported to riscv64 and riscv64sf (but it's l= ikely affected as well). > aarch64 is confirmed to be affected (so armv6 and armv7 are probably also= affected), but I don't have any way to test whether it works on aarch64 th= at way. >=20 > So currently limiting to powerpc*, but it will probably be extended to ar= mv*, aarch64 and riscv64* in the future. >=20 > > Otherwise it looks ok to me, but probably should be tested on a glibc n= on-x86 target. > >=20 > > In any case, this will be for the new branch, when stage 1 reopens. > >=20 > > FX >=20 > --=20 --=20 --ozKHMlGTKWz7p9Gt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEycyIeNkkgohzsoorelmbhSCDnJ0FAmJqylQACgkQelmbhSCD nJ3sfw//cpgUAVe4/xsEecu0mio9NaMl99Btvg1fxDKpBPOIgwhqm+zhETJZXZya wWYRjM6HZAaVUfWTTaBqWmxq6HIDk4SqtGg3eY97CWISrospEOedPCGxPV1+MkDB F+ESPOYSu9QuA9wPcCA681c5sJai3UNu5udt0bbZwa635e5P7FAuQpd4NfKnB3yS D+OKRjnAekGFKCsetA/KKIMXuoReOjOhj3Zo9p3IQeRVUnOjzNInxP2HU+ISyv6p Pqe6KhOLlHCk46pMlEMwXWnX1/QTDmhIDaXdyNRnDFBI4iA/metwSCXTjWbdHYXH qZ5BsPLMILDUH9i+PBXexp1k73ssZFKue0lakDHsixaEo/GyOGt+710ys/OAC9kF NAVpCefOhl4QHnTKGzEeQg7wA1PytSRGeDG6FZtgKW9eOwSrnx45l2eGoHDJRkWX 2FwwDvWy+CGRFPzq6PS4MJ0JCynagFxBb2l3trSxJ8Ig2ZNYEiOMPecdCQ8a0YAe qcrVnV4ZBlIP9QFQlCsXGpbdFochOT1XDUNfd/V84ULHGds3zIf4c4yx0ErGllqo mczXWOK+qF0r8nJqy6Iy6sGZZsawj20W5cOvKB+XbhlWs3H5V7e+g5FMvP/95Dy/ WNy/MK8JzSakW3P3RFhS0i25bcJ4ubuMfBKA1d7TZadIro74H2M= =tdZZ -----END PGP SIGNATURE----- --ozKHMlGTKWz7p9Gt--