From: Aditya Upadhyay <aadit0402@gmail.com>
To: newlib@sourceware.org
Subject: Re: Long double complex methods
Date: Thu, 29 Jun 2017 07:11:00 -0000 [thread overview]
Message-ID: <CAMZxAxfZuQL4XDpOPAHVFFtSdRejo8mZv=TC_4KXeUV8nMkjpQ@mail.gmail.com> (raw)
In-Reply-To: <20170629063911.GB31936@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
Hello Developers,
This is the modified patch for csinl.c which reflects changes in Makefile.am.
Thanks & Regards,
Aditya Upadhyay
On Thu, Jun 29, 2017 at 12:09 PM, Corinna Vinschen <vinschen@redhat.com> wrote:
> Hi Aditya,
>
> On Jun 29 02:04, Aditya Upadhyay 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,
> [...]
>
> Looks good, just the last patch in the series:
>
>> Subject: [PATCH 18/18] Importing csinl.c from NetBSD.
>
> is missing the Makefile.am change. Care to resend a v2 of patch 18?
>
>
> Thanks,
> Corinna
>
>
> --
> Corinna Vinschen
> Cygwin Maintainer
> Red Hat
[-- Attachment #2: 0018-Adding-csinl.c-in-Makefile.am.patch --]
[-- Type: text/x-patch, Size: 963 bytes --]
From 18ccb7b9ca0703b22443d87851b66e74270c1d54 Mon Sep 17 00:00:00 2001
From: Aditya Upadhyay <aadit0402@gmail.com>
Date: Thu, 29 Jun 2017 12:36:09 +0530
Subject: [PATCH v2 18/18] Adding csinl.c in Makefile.am
Signed-off-by: Aditya Upadhyay <aadit0402@gmail.com>
---
newlib/libm/complex/Makefile.am | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/newlib/libm/complex/Makefile.am b/newlib/libm/complex/Makefile.am
index 9f733e5..47b9662 100644
--- a/newlib/libm/complex/Makefile.am
+++ b/newlib/libm/complex/Makefile.am
@@ -14,7 +14,7 @@ lsrc = cabsl.c creall.c cimagl.c ccoshl.c cacoshl.c \
clogl.c csqrtl.c cargl.c cprojl.c cexpl.c \
cephes_subrl.c cacosl.c ccosl.c casinl.c \
catanhl.c conjl.c cpowl.c ctanhl.c ctanl.c \
- casinhl.c csinhl.c
+ casinhl.c csinhl.c csinl.c
fsrc = cabsf.c casinf.c ccosf.c cimagf.c cprojf.c \
csqrtf.c cacosf.c casinhf.c ccoshf.c clogf.c clog10f.c \
--
2.7.4
next prev parent reply other threads:[~2017-06-29 7:11 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
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 [this message]
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='CAMZxAxfZuQL4XDpOPAHVFFtSdRejo8mZv=TC_4KXeUV8nMkjpQ@mail.gmail.com' \
--to=aadit0402@gmail.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).