From: William Tambe <tambewilliam@gmail.com>
To: Jim Wilson <jimw@sifive.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Enable libgcc floating point emulation routines
Date: Wed, 21 Oct 2020 21:48:14 -0500 [thread overview]
Message-ID: <CAF8i9mPB3=KkkcH=-QDap8pHVa_3e870iG1L8n1GAqMmv9JAfg@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVaYR0uwE1QtzDRvZLxL_hfGENTUdJCYvYNN80RwhzfzwOg@mail.gmail.com>
On Wed, Oct 21, 2020 at 6:36 PM Jim Wilson <jimw@sifive.com> wrote:
>
> On Wed, Oct 21, 2020 at 1:27 PM William Tambe via Gcc-help <gcc-help@gcc.gnu.org> wrote:
>>
>> For a specific platform, what is the proper way to enable the floating
>> point emulation routines described at ?
>> https://gcc.gnu.org/onlinedocs/gccint/Soft-float-library-routines.html#Soft-float-library-routines
>
>
> In libgcc/config.host, add one of the t-softfp* files to tmake_file for your host. There are a number of choices, depending on exactly which modes you need support for, and exactly which modes are implemented in hardware. E.g. a target with no FP hardware and no 128-bit long double needs only soft-float sf and df. A target with FP hardware that supports 32-bit float only, and supports 128-bit long double, needs soft-float df and tf. Etc. See the various target independent and target dependent t-softfp files and pick one that matches your situation.
In libgcc/config.host we currently have:
tmake_file="${tmake_file} t-softfp-sfdf t-softfp-excl t-softfp"
However, compiling a program that uses __mulsf3() throws the following error:
error: implicit declaration of function ‘__mulsf3’; did you mean
‘__mulsc3’? [-Werror=implicit-function-declaration]
Compilation is done using -nostdlib -lgcc
Any idea what else is missing ?
>
> Jim
>
next prev parent reply other threads:[~2020-10-22 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 20:27 William Tambe
2020-10-21 23:36 ` Jim Wilson
2020-10-22 2:48 ` William Tambe [this message]
2020-10-22 3:40 ` William Tambe
2020-10-23 19:34 ` Jim Wilson
2020-10-23 19:33 ` Jim Wilson
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='CAF8i9mPB3=KkkcH=-QDap8pHVa_3e870iG1L8n1GAqMmv9JAfg@mail.gmail.com' \
--to=tambewilliam@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jimw@sifive.com \
/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).