public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Rodgers <trodgers@redhat.com>
To: "Dr. Matthias Kretz" <m.kretz@gsi.de>
Cc: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] std::experimental::simd
Date: Mon, 10 Feb 2020 20:14:00 -0000	[thread overview]
Message-ID: <xkqeeev2fbd9.fsf@trodgers.remote.f30> (raw)
In-Reply-To: <252496298.5185162.1581353329589.JavaMail.zimbra@redhat.com>

Erk, that was intended as a private reply.

Thomak Rodgers writes:

> Catching up on this...(and since I'm not in Prague I won't be able to do so in person).
>
> I finally got a chance to talk with Jeff Law recently about a more extensive testing strategy using Red Hat internal resources, and I am going to start working on
> adapting his CI build scripts that drive checking out machines from our lab environment starting later this week.
>
> Jonathan indicated you may have a newer version of your <simd> patch forthcoming? Is that something that's likely to happen before the end of this month? I'd
> like to work on getting start working on getting <simd> in during stage4 (Jonathan is willing to accept it because it is experimental as long as it is in
> good shape to commit).
>
> Thanks,
> Tom.
>
>
> ----- Original Message -----
> From: "Dr. Matthias Kretz" <m.kretz@gsi.de>
> To: trodgers@redhat.com
> Cc: libstdc++@gcc.gnu.org
> Sent: Thursday, October 24, 2019 1:26:47 AM
> Subject: Re: [PATCH] std::experimental::simd
>
> On Montag, 14. Oktober 2019 14:12:12 CEST Matthias Kretz wrote:
>> This patch is without documentation and testsuite. I can add them on request
>> but would prefer a follow-up patch after getting this one right.
>
> Regarding tests, here's what I think a "consumer test" should cover:
>
> 1. compiler flags
>   - `-march=native -O2`
>
> 2. element types
>   - char
>   - uint8_t
>   - int
>   - float
>   - double
>
> 3. operations
>   - broadcast ctor
>   - generator ctor
>   - all operators
>   - compares
>   - mask reductions
>   - non-converting loads & stores
>   - non-converting masked loads & stores
>   - horizontal reductions
>   - math: 1024 input values, comparing fun(T) against fun(simd<T>)
>   - conversions:
>     * char <-> int
>     * uint8_t <-> int
>     * uint8_t <-> float
>     * int <-> float
>     * int <-> double
>     * float <-> double
>
> 4. ABI tags:
>   - scalar
>   - fixed_size<{2, 3, 4, 6, 8, 12, 16, 32}>
>   - deduce_t<T, {2, 3, 4, 6, 8, 12, 16, 32}> (if different from fixed_size)
>   - deduce_t<T, 64> for AVX512BW targets
>   - compatible (if different from above)
>   - native (if different from above)
>
> Note that 1-4 are orthogonal and already span a huge space. I'm sure we need 
> to reduce this list, not expand.

  reply	other threads:[~2020-02-10 20:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 12:12 Matthias Kretz
2019-10-15  3:52 ` Thomas Rodgers
2019-10-24  8:26 ` Dr. Matthias Kretz
2020-02-10 16:49   ` Thomas Rodgers
2020-02-10 20:14     ` Thomas Rodgers [this message]
2020-01-07 11:01 ` Matthias Kretz
2020-01-07 11:17   ` Andrew Pinski
2020-01-07 13:19     ` Dr. Matthias Kretz
     [not found] ` <3486545.znU0eCzeS4@excalibur>
     [not found]   ` <xkqeo8qyl8y8.fsf@trodgers.remote>
2020-05-08 19:03     ` Matthias Kretz
2020-11-11 23:43       ` Jonathan Wakely
2020-11-14  1:11         ` Matthias Kretz
2020-11-15 19:11           ` Matthias Kretz
2020-12-10 21:13             ` Matthias Kretz

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=xkqeeev2fbd9.fsf@trodgers.remote.f30 \
    --to=trodgers@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=m.kretz@gsi.de \
    /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).