From: Corinna Vinschen <vinschen@redhat.com>
To: Jennifer Averett <jennifer.averett@oarcorp.com>
Cc: newlib@sourceware.org
Subject: Re: [PATCH 0/3]: Add math support for non LDBL_EQ_DBL architecture
Date: Wed, 5 Apr 2023 11:23:41 +0200 [thread overview]
Message-ID: <ZC0+HRh5qsxKcai3@calimero.vinschen.de> (raw)
In-Reply-To: <20230403205837.1595602-1-jennifer.averett@oarcorp.com>
Hi Jennifer,
On Apr 3 15:58, Jennifer Averett wrote:
> The attached set of patches add long double support for i386, aarch64 and
> x86_64. The riscv and powerpc are supported by FreeBSD but will need more
> work to be supported by newlib. FreeBSD has separate 64 and 32 bit powerpc
> support which would have to be integrated for newlib. FreeBSD riscv support
> is 64 and there are issues with fenv.h that would have to be addressed.
Thanks for your patchset, it looks pretty well to me, though I like
to have input on this from my co-maintainer Jeff, too.
I noticed that you exclude Cygwin from the new code, which makes sense
as long as we provide our own long double math taken from Mingw-w64.
However, there's something not quite right. When trying to build I get
symbol conflicts for the fdim{f,l} and scalbln{f,l} symbols in the link
stage (paths shortend for readability):
ld: libm.a(libm_a-s_fdim.o): in function `fdimf':
newlib/libm/ld/s_fdim.c:47: multiple definition of `fdimf'; libm.a(libm_a-sf_fdim.o):newlib/libm/common/sf_fdim.c:16: first defined here
ld: libm.a(libm_a-s_fdim.o): in function `fdiml':
newlib/libm/ld/s_fdim.c:48: multiple definition of `fdiml'; libdll.a(fdiml.o):winsup/cygwin/math/fdiml.c:11: first defined here
ld: libm.a(libm_a-s_scalbln.o): in function `scalblnf':
newlib/libm/ld/s_scalbln.c:46: multiple definition of `scalblnf'; libm.a(libm_a-sf_scalbln.o):newlib/libm/common/sf_scalbln.c:34: first defined here
ld: libm.a(libm_a-s_scalbln.o): in function `scalblnl':
newlib/libm/ld/s_scalbln.c:53: multiple definition of `scalblnl'; libdll.a(scalbnl.o):winsup/cygwin/scalbnl.S:19: first defined here
The conflicts really ony occur for these four functions. Any chance
to fix these?
Thanks,
Corinna
next prev parent reply other threads:[~2023-04-05 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 20:58 Jennifer Averett
2023-04-03 20:58 ` [PATCH 1/3] newlib: Add FreeBSD files for non LDBL_EQ_DBL support Jennifer Averett
2023-04-03 20:58 ` [PATCH 2/3] newlib: Add non LDBL_EQ_DBL math support for aarch64, i386, and x86_64 Jennifer Averett
2023-04-03 20:58 ` [PATCH 3/3] newlib: Regenerated source for adding non LDBL_EQ_DBL math methods Jennifer Averett
2023-04-05 9:23 ` Corinna Vinschen [this message]
2023-04-05 15:44 ` [PATCH 0/3]: Add math support for non LDBL_EQ_DBL architecture Joel Sherrill
2023-04-06 9:00 ` Corinna Vinschen
2023-04-06 14:06 ` Joel Sherrill
2023-04-06 16:23 ` Corinna Vinschen
2023-04-05 20:12 ` Jeff Johnston
2023-04-05 21:34 ` Joel Sherrill
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=ZC0+HRh5qsxKcai3@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jennifer.averett@oarcorp.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).