From: Piotr Kubaj <pkubaj@anongoth.pl>
To: FX <fxcoudert@gmail.com>
Cc: gcc-patches@gcc.gnu.org, Fortran List <fortran@gcc.gnu.org>,
segher@kernel.crashing.org
Subject: Re: [PATCH] fortran: use fpu-glibc on powerpc*-unknown-freebsd
Date: Thu, 14 Apr 2022 16:09:33 +0200 [thread overview]
Message-ID: <YlgrHYYfM4+F5MDx@KGPE-D16> (raw)
In-Reply-To: <DA245CDC-64F6-452F-AEE4-82F00C99783A@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On 22-04-14 09:05:17, FX wrote:
> Hi,
>
> > can you check the following patch?
>
> Why restrict it to powerpc-freebsd only, and not all freebsd? Do they differ?
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*, there are also armv6, armv7, aarch64, riscv64 and riscv64sf.
However, GCC is currently not ported to riscv64 and riscv64sf (but it's likely 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 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.
>
> In any case, this will be for the new branch, when stage 1 reopens.
>
> FX
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-04-14 14:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 15:30 FX
2022-04-13 14:56 ` Piotr Kubaj
2022-04-13 15:27 ` FX
2022-04-14 0:49 ` Piotr Kubaj
2022-04-14 7:05 ` FX
2022-04-14 14:09 ` Piotr Kubaj [this message]
2022-04-28 17:09 ` Piotr Kubaj
2022-04-28 18:55 ` FX
2022-04-30 18:28 ` Piotr Kubaj
2022-04-30 19:17 ` FX
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YlgrHYYfM4+F5MDx@KGPE-D16 \
--to=pkubaj@anongoth.pl \
--cc=fortran@gcc.gnu.org \
--cc=fxcoudert@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).