From: Corinna Vinschen <vinschen@redhat.com>
To: newlib@sourceware.org
Subject: Re: [PATCH] RISC-V: Use newlib nano specific libm.
Date: Fri, 31 Jan 2020 11:42:00 -0000 [thread overview]
Message-ID: <20200131114203.GV3549@calimero.vinschen.de> (raw)
In-Reply-To: <20200129224617.14207-1-jimw@sifive.com>
[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]
On Jan 29 14:46, Jim Wilson wrote:
> The libm gamma functions use the _gamma_signgam field of the reentrant
> structure, which changes offset with the --enable-newlib-reent-small
> configure option, which means we need to use a newlib nano specific
> version of libm in addition to libc in the nano.specs file. Reported
> by Keith Packard. There is a riscv-gnu-toolchain patch that goes
> along with this to create the new libm_nano.a file.
>
> Signed-off-by: Jim Wilson <jimw@sifive.com>
> ---
> libgloss/riscv/nano.specs | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libgloss/riscv/nano.specs b/libgloss/riscv/nano.specs
> index 89fd23176..e12e31384 100644
> --- a/libgloss/riscv/nano.specs
> +++ b/libgloss/riscv/nano.specs
> @@ -15,7 +15,7 @@
> %(nano_link_gcc_c_sequence) --start-group %G %(nano_libc) %(nano_libgloss) --end-group
>
> *link:
> -%(nano_link) %:replace-outfile(-lc -lc_nano) %:replace-outfile(-lg -lg_nano)
> +%(nano_link) %:replace-outfile(-lc -lc_nano) %:replace-outfile(-lg -lg_nano) %:replace-outfile(-lm -lm_nano)
>
> *lib:
> %{!shared:%{g*:-lg_nano} %{!p:%{!pg:-lc_nano}}%{p:-lc_p}%{pg:-lc_p}}
> --
> 2.17.1
Pushed.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2020-01-31 11:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 22:46 Jim Wilson
2020-01-31 11:42 ` Corinna Vinschen [this message]
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=20200131114203.GV3549@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=newlib@sourceware.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).