From: Eshan Dhawan <eshandhawan51@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>, Joel Sherrill <joel@rtems.org>
Subject: Re: [PATCH] Remove multiple defination error
Date: Sat, 11 Jul 2020 22:48:13 +0530 [thread overview]
Message-ID: <CAH5ZSWqxb_UBPRqdoGc==ozjPjSHHwmwyr2pYwiK8+7hso3gZg@mail.gmail.com> (raw)
In-Reply-To: <5de6b501-b0a2-68a6-b5b2-6fb487506f3b@embedded-brains.de>
On Sat, Jul 11, 2020 at 8:46 PM Sebastian Huber <
sebastian.huber@embedded-brains.de> wrote:
> On 11/07/2020 00:41, Eshan dhawan wrote:
>
> > Signed-off-by: Eshan dhawan<eshandhawan51@gmail.com>
> > ---
> > newlib/libm/machine/arm/fenv-vfp.c | 7 ++++-
> > newlib/libm/machine/arm/fenv.c | 47 +++++++++++++++++++-----------
> > 2 files changed, 36 insertions(+), 18 deletions(-)
>
> What are the design goals of this implementation? Should it work with
> some sort of run time VFP detection? Should it select the support using
> builtin defines?
>
It used the GCC flags to detect VPF
if VPF is not selected all the symbols of vfp won't appear :)
>
> I would use builtin defines only and then just use a single file.
>
I tried converting into a single file but the file becomes too complex to
handle and check for errors. :)
next prev parent reply other threads:[~2020-07-11 17:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-10 22:41 Eshan dhawan
2020-07-11 15:16 ` Sebastian Huber
2020-07-11 17:18 ` Eshan Dhawan [this message]
2020-07-13 5:36 ` Sebastian Huber
2020-07-13 5:48 ` Sebastian Huber
2020-07-14 13:11 ` Joel Sherrill
2020-07-14 16:59 ` Jim Wilson
2020-07-14 17:51 ` Sebastian Huber
2020-07-23 11:54 Eric Bresie
2020-07-23 12:04 ` Sebastian Huber
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='CAH5ZSWqxb_UBPRqdoGc==ozjPjSHHwmwyr2pYwiK8+7hso3gZg@mail.gmail.com' \
--to=eshandhawan51@gmail.com \
--cc=joel@rtems.org \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).