public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Kito Cheng <kito.cheng@sifive.com>
To: newlib@sourceware.org, kito.cheng@gmail.com
Cc: Kito Cheng <kito.cheng@sifive.com>
Subject: [PATCH 2/2] RISC-V: Fix wrong including file in s_isinf.c
Date: Wed, 28 Oct 2020 23:41:27 +0800	[thread overview]
Message-ID: <20201028154127.41565-2-kito.cheng@sifive.com> (raw)
In-Reply-To: <20201028154127.41565-1-kito.cheng@sifive.com>

---
 newlib/libm/machine/riscv/s_isinf.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/newlib/libm/machine/riscv/s_isinf.c b/newlib/libm/machine/riscv/s_isinf.c
index 3c82ee268..3d6d685a3 100644
--- a/newlib/libm/machine/riscv/s_isinf.c
+++ b/newlib/libm/machine/riscv/s_isinf.c
@@ -48,5 +48,5 @@ isinf (double x)
 	return (fclass & FCLASS_INF);
 }
 #else
-#include "../../common/sf_isinf.c"
+#include "../../common/s_isinf.c"
 #endif
-- 
2.28.0


  reply	other threads:[~2020-10-28 15:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-28 15:41 [PATCH 1/2] RISC-V: NaN should return 0 for finite[f] Kito Cheng
2020-10-28 15:41 ` Kito Cheng [this message]
2020-10-29  8:41 ` Corinna Vinschen
2020-10-29  9:46   ` Kito Cheng

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=20201028154127.41565-2-kito.cheng@sifive.com \
    --to=kito.cheng@sifive.com \
    --cc=kito.cheng@gmail.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).