public inbox for newlib@sourceware.org
 help / color / mirror / Atom feed
From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Dionna Amalie Glaze <dionnaglaze@google.com>,
	Aditya Upadhyay <aadit0402@gmail.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: Long double complex methods
Date: Wed, 28 Jun 2017 21:57:00 -0000	[thread overview]
Message-ID: <f8e36f0e-ab65-6aa0-2d0c-0750de7ec57c@oarcorp.com> (raw)
In-Reply-To: <CAAH4kHbk0ACL7uGYAy4PaXD=_rPDviO08y=Zcn9J3vLO2oweKA@mail.gmail.com>



On 6/28/2017 4:36 PM, Dionna Amalie Glaze via newlib wrote:
> Gave it a quick look-over (I'm not a core dev, but figured I'd look
> since you seem eager). It looks like everything is indeed from the
> current NetBSD codebase.
> 
> cacoshl.c has #if 0'd code that probably shouldn't be checked in? The
> #if 0 is directly from NetBSD, but still #if 0s aren't nice.
> 
> clogl.c why not use cargl(z) for rr? The compiler would inline it, and
> arg(z) is closer to the math.
> 
> cprojl.c More of a note to others: I was confused why you would use
> HUGE_VAL instead of __INFINITY, but apparently that was a conscious
> change here http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libm/complex/cprojl.c?rev=1.6&content-type=text/x-cvsweb-markup&only_with_tag=MAIN
> from http://cvsweb.netbsd.org/bsdweb.cgi/src/lib/libm/complex/cprojl.c?rev=1.5&content-type=text/x-cvsweb-markup&only_with_tag=MAIN

I can't argue the rationale for any of the above except to
say that the goal is to import unmodified source from
third party sources. Newlib generally trusts that the
upstream sources are "reputable".


> 
> Would you please include additions to libm/test/ for your included
> functionality? That probably should be upstreamed to NetBSD too, since
> I see they have no tests *gasp*
> http://www.mirrorservice.org/pub/NetBSD/NetBSD-current/src/tests/lib/libm/

Agreed they need tests but that would be a NetBSD issue.

Also, although I don't know how to run them, doesn't someone
run glibc tests on newlib? They likely have tests for this for
newlib's purposes.

<hint>I would like to know how to run then</hint> :)

Aditya.. file a NetBSD ticket with the list of methods they
don't have any tests for. I may have to get a NetBSD account
so I can track the ticket.

FWIW Aditya is a Google Summer of Code student for RTEMS working
to improve POSIX compliance for newlib and by implication
RTEMS and Cygwin. Issues with upstream sources with the code
should be filed upstream.


> On Wed, Jun 28, 2017 at 1:34 PM, Aditya Upadhyay <aadit0402@gmail.com> wrote:
>> Hello Developers,
>>
>> I have ported all long double complex methods with suffix "l" from
>> NetBSD. I am attaching the patches for all the methods. I am
>> requesting you to please review these patches and point me any
>> modification needed.
>>
>> Thanks & Regards,
> 
> 
> 

  reply	other threads:[~2017-06-28 21:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28 20:35 Aditya Upadhyay
2017-06-28 21:36 ` Dionna Amalie Glaze via newlib
2017-06-28 21:57   ` Joel Sherrill [this message]
2017-06-29 16:18     ` Joseph Myers
2017-06-29 16:31       ` Joel Sherrill
2017-06-29  6:39 ` Corinna Vinschen
2017-06-29  7:11   ` Aditya Upadhyay
2017-06-29 11:53     ` Corinna Vinschen
2017-06-29 12:04       ` Corinna Vinschen
2017-06-29 19:38         ` Yaakov Selkowitz
2017-06-29 21:17           ` Joel Sherrill
2017-06-30  9:11             ` Aditya Upadhyay
2017-07-04 21:31               ` Aditya Upadhyay
2017-07-04 21:56                 ` Aditya Upadhyay
2017-07-05  8:27                   ` Corinna Vinschen
2017-07-05  9:02                     ` Aditya Upadhyay
2017-07-05 12:40                       ` Corinna Vinschen
2022-11-08 18:31                       ` [newlib] Generally make all 'long double complex' methods available in <complex.h> Thomas Schwinge
2022-11-08 20:24                         ` Jeff Johnston
2017-06-29 13:47   ` Long double complex methods Joel Sherrill
  -- strict thread matches above, loose matches on Subject: below --
2017-06-28 13:53 Aditya Upadhyay

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=f8e36f0e-ab65-6aa0-2d0c-0750de7ec57c@oarcorp.com \
    --to=joel.sherrill@oarcorp.com \
    --cc=aadit0402@gmail.com \
    --cc=dionnaglaze@google.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).