From: Florian Weimer <fweimer@redhat.com>
To: GT <tnggil@protonmail.com>
Cc: Bill Schmidt <wschmidt@linux.ibm.com>,
"libc-alpha\@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: PPC64 libmvec sincos/sincosf ABI
Date: Thu, 08 Aug 2019 17:56:34 +0200 [thread overview]
Message-ID: <877e7nabwt.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <o17n2W1DqXwe_xbYdJAHVu4M5Y5KjVg-HUwQeaB1HLGk7FUCBKIEvYYO-50725OnNY2gDtfpkfHxkdd3tJMWDHAjddPcFGDNPefYX3fN-qE=@protonmail.com> (GT's message of "Thu, 08 Aug 2019 15:48:22 +0000")
* GT:
> ./tst_sincos.c: In function ‘main’:
> ./tst_sincos.c:15:5: warning: implicit declaration of function ‘sincos’ [-Wimplicit-function-declaration]
> sincos (a[i], &b[i], &c[i]);
> ^~~~~~
> ./tst_sincos.c:15:5: warning: incompatible implicit declaration of built-in function ‘sincos’
> ./tst_sincos.c:15:5: note: include ‘<math.h>’ or provide a declaration of ‘sincos’
> ./tst_sincos.c:2:1:
> +#include <math.h>
For sincos, you currently need to build with _GNU_SOURCE. (I don't get
a vector call for this, though.)
We should probably make sincos etc. available by default because these
functions are widely available elsewhere.
Thanks,
Florian
next prev parent reply other threads:[~2019-08-08 15:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 13:01 PPC64 libmvec sincos/sincosf ABI GT
2019-08-01 17:04 ` Joseph Myers
2019-08-07 21:17 ` Tulio Magno Quites Machado Filho
2019-08-08 13:33 ` Bill Schmidt
2019-08-08 15:48 ` GT
2019-08-08 15:56 ` Florian Weimer [this message]
2019-08-08 16:56 ` GT
2019-08-08 16:11 ` Bill Schmidt
2019-08-08 17:42 ` GT
2019-08-08 17:51 ` Bill Schmidt
-- strict thread matches above, loose matches on Subject: below --
2019-08-06 17:42 Wilco Dijkstra
2019-08-06 20:31 ` Joseph Myers
2019-08-08 15:25 ` Bill Schmidt
2019-08-08 18:48 ` Bill Schmidt
2019-09-20 19:25 ` GT
2019-09-20 20:25 ` Bill Schmidt
2019-09-23 18:02 ` GT
2019-09-24 16:43 ` Bill Schmidt
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877e7nabwt.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=tnggil@protonmail.com \
--cc=wschmidt@linux.ibm.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).