From: Matthias Kretz <m.kretz@gsi.de>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Thomas Rodgers <trodgers@redhat.com>,
libstdc++ <libstdc++@gcc.gnu.org>,
Gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] std::experimental::simd
Date: Sun, 15 Nov 2020 20:11:35 +0100 [thread overview]
Message-ID: <6068814.e9AK2G76lq@excalibur> (raw)
In-Reply-To: <7016866.CdeeP7ohKn@excalibur>
[-- Attachment #1: Type: text/plain, Size: 1146 bytes --]
On Samstag, 14. November 2020 02:11:04 CET Matthias Kretz wrote:
> Thanks. I'll post a new patch ASAP. My tests are running.
(The tests found that std::__bit_width is off by one for what I needed; and
the fix to __is_narrowing_conversion for bool broke the simd broadcast ctor.)
New patch attached (against the gcc-10 branch).
You can also see the patch on GitHub: https://github.com/gcc-mirror/gcc/
compare/releases/gcc-10...mattkretz:mkretz/simd2
Cheers,
Matthias
--
──────────────────────────────────────────────────────────────────────────
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
──────────────────────────────────────────────────────────────────────────
[-- Attachment #2: simd-2020-11-15.patch.zip --]
[-- Type: application/zip, Size: 226080 bytes --]
next prev parent reply other threads:[~2020-11-15 19:11 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
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 [this message]
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=6068814.e9AK2G76lq@excalibur \
--to=m.kretz@gsi.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=trodgers@redhat.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).