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 3ADC53858016; Thu, 14 Apr 2022 14:09:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 3ADC53858016 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 7B5251979D6; Thu, 14 Apr 2022 16:09:34 +0200 (CEST) Date: Thu, 14 Apr 2022 16:09:33 +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="oRV0Ln1Vp6JUWLVx" Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE 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, 14 Apr 2022 14:09:41 -0000 --oRV0Ln1Vp6JUWLVx Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 dif= fer? amd64 and i386 on all systems use a different setting and are not affected. For FreeBSD-supported architectures that are not amd64, i386 or powerpc*, t= here are also armv6, armv7, aarch64, riscv64 and riscv64sf. However, GCC is currently not ported to riscv64 and riscv64sf (but it's lik= ely affected as well). aarch64 is confirmed to be affected (so armv6 and armv7 are probably also a= ffected), but I don't have any way to test whether it works on aarch64 that= way. So currently limiting to powerpc*, but it will probably be extended to armv= *, aarch64 and riscv64* in the future. > Otherwise it looks ok to me, but probably should be tested on a glibc non= -x86 target. >=20 > In any case, this will be for the new branch, when stage 1 reopens. >=20 > FX --=20 --oRV0Ln1Vp6JUWLVx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEycyIeNkkgohzsoorelmbhSCDnJ0FAmJYKx0ACgkQelmbhSCD nJ3ZChAAva4EPW+acj1iQT5GD1fMyoooJ1M/pR2Pz3T1D9syRvNzK313qqmj3Xlb AHhjixWMDWmACFVZ/Bktq/0SpvnRUQCqRSJaEuevJZ8k5RYwQlg8M7UufUeB4wwP WrrTEoRrvjr3/UFpfrrp6rHeIhN3rGEXE8+EQhixwaUGNpObaFh+npIBe31JU96E xjuCJH9QRtR9aK+d2PgZhrZybWaEcD1q7Bgx/FvMRzxWDmtYEK1SBqk+Jd7R5n5f JclcQh6WW4ODiwuGsXi5Fnxemed/E9cZcjLZttmFmA6Hgbxn/TzdJQBlRCuOPpMn PV17lRVdqg/eStcSSh5jXG5DMKNJ+XjN1zu4zmbS5UEU8dLZbcfsO2LLJtM1YM9M nJwPthyYWcf1aSLs6dwCNVD4WLNuH07b90TnBCC7sk1N6FFJEyZKyTZKPtjHSqli W/5kqidzvecOAihWM6wepikKJ2KxmUy6huhlJWdCyv9VrrL8PoTtc4Zh5YogsMFg ELuAUdmJ+6I81fq/m0JBAZ+Gn/5pbh51X/65pmJHddNdzeU2iXnOkyr8H10lZPof VdckuIjkpATPyaOMBWvuhyw1/sc0fTa2PZ1I42zviTvenV8ULmATw1f/O3pPV07z NHJgm2j2bF8E6Pq60PcXXe6xSrbNwqlExcFlxHyi7wdTIeHk+hU= =I/10 -----END PGP SIGNATURE----- --oRV0Ln1Vp6JUWLVx--