public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Thomas Rodgers <trodgers@redhat.com>
To: libstdc++@gcc.gnu.org
Subject: Re: [PATCH] std::experimental::simd
Date: Tue, 15 Oct 2019 03:52:00 -0000	[thread overview]
Message-ID: <xkqe5zkqy8b4.fsf@trodgers.remote.f30> (raw)
In-Reply-To: <10916085.4XdQGCaa7L@depc447>

Hey Matthias,

Sorry about missing you in Cologne. I have been meaning to send a
followup email. I'd like to start the review of this patch but I don't
think I'll have time before the close of stage 1, as I have a few C++20
features I'm trying to finish by the end of the month.

Can we set up a bit of time early next week to discuss this? I can
arrange BlueJeans teleconference.

Thanks,
Tom.

Matthias Kretz writes:

> Let me try again to get this patch ready. It will need a few iterations... 
> 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.
>
> I recommend to review starting from simd.h + simd_scalar.h, then 
> simd_builtin.h, simd_x86.h, and simd_fixed_size.h. I sure when we get this far 
> we are a few iterations further.
>
> Regarding the license. The license header is currently just a copy from my 
> repo, but we can change it to the libstdc++ license. The paperwork with the 
> FSF is done.
>
>
> 	* include/Makefile.am: Add new header.
> 	* include/Makefile.in: Regenerate.
> 	* include/experimental/simd: New header for Parallelism TS 2.
> 	* include/experimental/bits/simd.h: Definition of the public simd
> 	interfaces and general implementation helpers.
> 	* include/experimental/bits/simd_builtin.h: Implementation of the
> 	_VecBuiltin simd_abi.
> 	* include/experimental/bits/simd_combine.h: Preliminary
> 	implementation of the _Combine simd_abi.
> 	* include/experimental/bits/simd_converter.h: Generic simd
> 	conversions.
> 	* include/experimental/bits/simd_detail.h: Internal macros for the
> 	simd implementation.
> 	* include/experimental/bits/simd_fixed_size.h: Simd fixed_size ABI
> 	specific implementations.
> 	* include/experimental/bits/simd_math.h: Math overloads for simd.
> 	* include/experimental/bits/simd_neon.h: Simd NEON specific
> 	implementations.
> 	* include/experimental/bits/simd_scalar.h: Simd scalar ABI
> 	specific implementations.
> 	* include/experimental/bits/simd_x86.h: Simd x86 specific
> 	implementations.
> 	* include/experimental/bits/simd_x86_conversions.h: x86 specific
> 	conversion optimizations.

  reply	other threads:[~2019-10-15  3:52 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 [this message]
2019-10-24  8:26 ` Dr. Matthias Kretz
2020-02-10 16:49   ` Thomas Rodgers
2020-02-10 20:14     ` Thomas Rodgers
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=xkqe5zkqy8b4.fsf@trodgers.remote.f30 \
    --to=trodgers@redhat.com \
    --cc=libstdc++@gcc.gnu.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).