public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Kretz <m.kretz@gsi.de>
To: libstdc++ <libstdc++@gcc.gnu.org>
Cc: yaozhongxiao <yaozhongxiao@linux.alibaba.com>
Subject: Re: [RFC]  libstc++: Implement gather and scatter
Date: Fri, 19 Feb 2021 10:12:17 +0100	[thread overview]
Message-ID: <2558942.OtKeevKjdC@excalibur> (raw)
In-Reply-To: <8bf771b0-3a95-4256-93c4-163ad71cea42.yaozhongxiao@linux.alibaba.com>

Thank you! But please just call me Matthias :)

I already gave feedback at https://github.com/VcDevel/std-simd/pull/27. But 
I'd like to raise the issue of not-yet-proposed-but-we-want-to-write-a-paper-
soon features.

My understanding: If we define interfaces without using reserved names we're 
risking a source incompatible change (i.e. user code doesn't compile anymore 
after libstdc++ was modified to match the WG21 paper). I've seen non-standard 
extensions in libstdc++ use e.g. __member_function(...). I.e. without the _M_ 
or _S_ prefix. Is this the way to go? What about non-standard constructor 
overloads? We can't introduce a reserved name except via a tag type. 
Alternatively we could use a static function.

Cheers,
  Matthias

On Donnerstag, 18. Februar 2021 14:12:14 CET yaozhongxiao via Libstdc++ wrote:
> Memory load/store in gather and scatter mode with simd are common cases.
> I try to support the gather and scatter features in my workload.
> I send my draft to request for comment and suggestions before officially
> commits, Please do not hesitate to correct and comment, thanks.
> 
> Dr. Matthias Kretz, thank you very much for your work in simd,
> and hope to look forward to get suggestion from you.
> 
> --------------------------------------------------------------
>  libstc++: Implement gather and scatter
>     memory load/store in gather and scatter mode with simd are common
>     cases. Implement them in simd via call to _S_gather and _S_scatter
>     with it's Abi method.
> 
>     libstdc++-v3/ChangeLog:
> 
>             * include/experimental/bits/simd.h: Add simd::gather and
>             simd::scatter as the public methods.
>             * include/experimental/bits/simd_builtin.h: Add
>             _SimdImplBuiltin::_S_gather and _SimdImplBuiltin::_S_scatter
>             for simd native abi implementation.
>             * include/experimental/bits/simd_fixed_size.h: Add
>             _SimdImplFixedSize::_S_gather and _SimdImplFixedSize::_S_scatter
> for simd fix abi implementation;
>             _SimdTuple::_M_tuple_at for tuple accessing
>             * include/experimental/bits/ssimd_scalar: Add
>             _SimdImplScalar::_S_gather and _SimdImplScalar::_S_scatter
>             for simd scalar abi implementation.


-- 
──────────────────────────────────────────────────────────────────────────
 Dr. Matthias Kretz                           https://mattkretz.github.io
 GSI Helmholtz Centre for Heavy Ion Research               https://gsi.de
 std::experimental::simd              https://github.com/VcDevel/std-simd
──────────────────────────────────────────────────────────────────────────

  reply	other threads:[~2021-02-19  9:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-18 13:12 yaozhongxiao
2021-02-19  9:12 ` Matthias Kretz [this message]
2021-02-19 12:56   ` yao zhongxiao

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=2558942.OtKeevKjdC@excalibur \
    --to=m.kretz@gsi.de \
    --cc=libstdc++@gcc.gnu.org \
    --cc=yaozhongxiao@linux.alibaba.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).