From: Carlos O'Donell <carlos@redhat.com>
To: Joseph Myers <joseph@codesourcery.com>,
Andrew Senkevich <andrew.n.senkevich@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH x86-64][BZ #20024] Fixed vector sincos/sincosf ABI
Date: Tue, 07 Jun 2016 00:02:00 -0000 [thread overview]
Message-ID: <57560F10.4040907@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1606061404540.15183@digraph.polyomino.org.uk>
On 06/06/2016 10:08 AM, Joseph Myers wrote:
> C tests seem safer where possible. For example: the existing functions
> are said to take vectors of pointers. Does that mean vectors of 8-byte
> pointers for the 64-bit ABI and vectors of 4-byte pointers for x32? If
> so, a C test is more likely to get right that the ABI to test is different
> in those cases.
+1
--
Cheers,
Carlos.
next prev parent reply other threads:[~2016-06-07 0:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-31 19:41 Andrew Senkevich
2016-06-01 0:15 ` Carlos O'Donell
2016-06-01 20:03 ` Andrew Senkevich
2016-06-02 22:50 ` Joseph Myers
2016-06-06 13:35 ` Andrew Senkevich
2016-06-06 14:08 ` Joseph Myers
2016-06-07 0:02 ` Carlos O'Donell [this message]
2016-06-11 12:56 ` Andrew Senkevich
2016-06-18 10:03 ` Andrew Senkevich
2016-06-22 15:13 ` Joseph Myers
2016-06-22 17:53 ` Andrew Senkevich
2016-06-22 17:57 ` Joseph Myers
2016-06-23 16:33 ` Andrew Senkevich
2016-06-27 11:26 ` Andrew Senkevich
2016-06-29 21:59 ` Joseph Myers
2016-06-30 12:41 ` Andrew Senkevich
2016-06-30 13:47 ` Joseph Myers
2016-06-30 15:22 ` Andrew Senkevich
2016-06-30 22:26 ` Joseph Myers
2016-07-01 11:53 ` Andrew Senkevich
2016-07-01 16:15 ` Joseph Myers
2016-07-04 12:14 ` Andrew Senkevich
2016-07-08 14:08 ` Andrew Senkevich
2016-07-08 16:20 ` Adhemerval Zanella
2016-06-30 11:44 ` Andrew Senkevich
2016-06-30 12:36 ` Andrew Senkevich
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=57560F10.4040907@redhat.com \
--to=carlos@redhat.com \
--cc=andrew.n.senkevich@gmail.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@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).