From: "chengzhiwei (C)" <chengzhiwei6@huawei.com>
To: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: disable-newlib-io-long-double?
Date: Mon, 16 Mar 2020 11:37:06 +0000 [thread overview]
Message-ID: <7D9266CBFB4E9A4B9C7B1D0341567D860173083C@DGGEMI529-MBX.china.huawei.com> (raw)
Hi, all:
In my project, all of the quadrature symbols have been stripped away in libgcc.a, so when I built newlib toolchain based on riscv32 target, we used the option "--disable-newlib-io-long-double" to turn off the feature of long double. But when performing a floating-point calculation, the symbol "trunctfdf2" is not defined correctly:
libc.a(lib_a-vfprintf.o): in function `.L60':vfprintf.c:(.text+0x3fe): undefined reference to `__trunctfdf2'
What puzzles me is why is this one symbol undefined? Is there any way to solve this problem?
Regards,
--zhiwei
next reply other threads:[~2020-03-16 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-16 11:37 chengzhiwei (C) [this message]
2020-03-16 20:50 ` disable-newlib-io-long-double? Jim Wilson
2020-03-17 1:34 disable-newlib-io-long-double? chengzhiwei (C)
2020-03-17 18:10 ` disable-newlib-io-long-double? 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=7D9266CBFB4E9A4B9C7B1D0341567D860173083C@DGGEMI529-MBX.china.huawei.com \
--to=chengzhiwei6@huawei.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).