public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/100662] intrinsic::ieee_arithmetic fails on aarch, powerpc architectures on FreeBSD
Date: Wed, 19 May 2021 01:10:09 +0000 [thread overview]
Message-ID: <bug-100662-4-eXQ7iZvhbw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100662-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, May 19, 2021 at 12:56:57AM +0000, yuri at tsoft dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100662
>
> --- Comment #5 from Yuri <yuri at tsoft dot com> ---
> config.log doesn't contain the IEEE string even on amd64.
>
> libgfortran/configure.host seems to only enable IEEE modules on i?86 | x86_64
> architectures through this code:
>
> > case "${host_cpu}" in
> > i?86 | x86_64)
> > if test "x${have_soft_float}" = "xyes"; then
> > fpu_host='fpu-generic'
> > else
> > fpu_host='fpu-387'
> > fi
> > ieee_support='yes'
> > ;;
> > esac
>
> What does gcc need from OS for IEEE754?
> Shouldn't it just compile with relevant to IEEE754 opcodes?
>
In
x86_64-unknown-freebsd14.0/libgfortran/config.log
I see
configure:26522: FPU dependent file will be fpu-387.h
configure:26524: Support for IEEE modules: yes
Looking at libgfortran/configure and libgfortran/configure.host
and looking in libgfortran/config/, it seems you'll need to define
an fpu-aarch64.h
I don't have an aarch64 system nor access to such a system,
so can't help you more.
next prev parent reply other threads:[~2021-05-19 1:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 19:13 [Bug fortran/100662] New: " yuri at tsoft dot com
2021-05-18 22:24 ` [Bug fortran/100662] " kargl at gcc dot gnu.org
2021-05-18 22:27 ` yuri at tsoft dot com
2021-05-18 22:47 ` yuri at tsoft dot com
2021-05-19 0:23 ` sgk at troutmask dot apl.washington.edu
2021-05-19 0:56 ` yuri at tsoft dot com
2021-05-19 1:10 ` sgk at troutmask dot apl.washington.edu [this message]
2021-05-19 1:43 ` yuri at tsoft dot com
2021-05-19 2:26 ` sgk at troutmask dot apl.washington.edu
2021-05-19 9:45 ` ripero84 at gmail dot com
2021-05-19 15:19 ` sgk at troutmask dot apl.washington.edu
2021-05-25 19:34 ` ripero84 at gmail dot com
2021-08-12 19:12 ` gerald at pfeifer dot com
2021-08-12 20:04 ` andreast at gcc dot gnu.org
2021-08-12 20:56 ` kargl at gcc dot gnu.org
2021-08-29 20:31 ` andreast at gcc dot gnu.org
2022-05-16 14:20 ` pkubaj at anongoth dot pl
2022-09-10 13:47 ` vital.had at gmail dot com
2024-06-13 9:51 ` vital.had at gmail dot com
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=bug-100662-4-eXQ7iZvhbw@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).