public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] RISC-V: Use newlib nano specific libm.
Date: Fri, 31 Jan 2020 11:43:00 -0000	[thread overview]
Message-ID: <20200131114311.50742.qmail@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=8ef32f2dcfe48b540e64a4ec3ce0dcba5d3b70ce

commit 8ef32f2dcfe48b540e64a4ec3ce0dcba5d3b70ce
Author: Jim Wilson <jimw@sifive.com>
Date:   Wed Jan 29 14:46:17 2020 -0800

    RISC-V: Use newlib nano specific libm.
    
    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>

Diff:
---
 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 89fd231..e12e313 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}}


                 reply	other threads:[~2020-01-31 11:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20200131114311.50742.qmail@sourceware.org \
    --to=corinna@sourceware.org \
    --cc=newlib-cvs@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).