From: Corinna Vinschen <vinschen@redhat.com>
To: Jeff Johnston <jjohnstn@redhat.com>
Cc: Newlib <newlib@sourceware.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
nd@arm.com
Subject: Re: [PATCH v2] New expf, exp2f, logf, log2f and powf implementations
Date: Fri, 13 Oct 2017 09:15:00 -0000 [thread overview]
Message-ID: <20171013091326.GC20139@calimero.vinschen.de> (raw)
In-Reply-To: <CAOox84tXBdsQ-esL4HWWnOe0e+EhDSrSTS+AV4LcrzmJoOt+sw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2302 bytes --]
On Oct 11 12:28, Jeff Johnston wrote:
> On Wed, Oct 11, 2017 at 8:05 AM, Corinna Vinschen <vinschen@redhat.com>
> wrote:
>
> > On Sep 29 11:41, Szabolcs Nagy wrote:
> > > On 05/09/17 09:38, Corinna Vinschen wrote:
> > > > Ok, I retract my reservations against OBSOLETE_MATH as such. However,
> > > > there are a few problems with the current patch:
> > > >
> > > > - Rename to __OBSOLETE_MATH (two underscores) so as not to spoil the
> > > > namespace.
> > > >
> > > > - The current implementation disallows a developer to override the
> > > > setting from, e. g., sys/config.h or the command line. As a minimum,
> > > > __OBSOLETE_MATH should only be set if it isn't already set, and the
> > > > checks for __OBSOLETE_MATH should check for being != 0:
> > > >
> > > > - #define __TGT_OBSOLETE_MATH 1 in arm and aarch cases
> > > >
> > > > - At the end of the file
> > > >
> > > > #ifndef __OBSOLETE_MATH
> > > > #define __OBSOLETE_MATH __TGT_OBSOLETE_MATH
> > > > #endif
> > > >
> > > > - Further checks in the code:
> > > >
> > > > #if __OBSOLETE_MATH
> > > >
> > > > rather than
> > > >
> > > > #ifdef __OBSOLETE_MATH
> > > >
> > > > - The header of ieeefp.h explains the options. Add
> > __TGT_OBSOLETE_MATH /
> > > > __OBSOLETE_MATH and add an informative comment along the lines of the
> > > > above text, so developers have enough info to decide if they want to
> > > > enable this for their target.
> > > >
> > > > Not sure if __TGT_OBSOLETE_MATH is a good name, though. I'm open for
> > > > better suggestions.
> > > >
> > >
> > > i used __OBSOLETE_MATH_DEFAULT.
> > >
> > > v2:
> > > - Use __OBSOLETE_MATH and __OBSOLETE_MATH_DEFAULT.
> > > - Upstream change: whitespace code style fixes.
> > > - Upstream change: HIDDEN attribute for data symbols.
> > > - Upstream change: __logf_data.poly array size is reduced.
> > > - Upstream change: issignalingf_inline now has code for non-standard
> > SNaN.
> >
> > The above points have been fixed, so I'm ok with the change if
> > it makes sense from an FP point of view. Jeff?
> >
>
> I am fine with it. Please go ahead.
You have push perms, too ;)
Pushed.
Thanks,
Corinna
--
Corinna Vinschen
Cygwin Maintainer
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-10-13 9:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-05 8:39 [RFC][PATCH] " Wilco Dijkstra
2017-09-06 6:58 ` Corinna Vinschen
2017-09-29 18:45 ` [PATCH v2] " Szabolcs Nagy
2017-10-11 11:57 ` Szabolcs Nagy
2017-10-11 12:58 ` Corinna Vinschen
2017-10-13 1:31 ` Jeff Johnston
2017-10-13 9:15 ` Corinna Vinschen [this message]
2017-10-17 13:01 ` Szabolcs Nagy
2017-10-19 1:01 ` Szabolcs Nagy
2017-10-23 17:16 ` Corinna Vinschen
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=20171013091326.GC20139@calimero.vinschen.de \
--to=vinschen@redhat.com \
--cc=jjohnstn@redhat.com \
--cc=nd@arm.com \
--cc=newlib@sourceware.org \
--cc=szabolcs.nagy@arm.com \
/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).