On Thu, Aug 4, 2022 at 12:38 PM Masahiko Sawada
wrote:
>
> I also think it's a good start. There is a typo in the commit message:
>
> s/hepler/helper/
>
> The rest looks good to me.
Fixed, and pushed, thanks to you both! I'll polish a small patch I have
that actually uses this.
--
John Naylor
Hi,
On Wed, Aug 3, 2022 at 2:01 PM John Naylor wrote:
>
>
> On Tue, Aug 2, 2022 at 11:53 PM Nathan Bossart
> wrote:
> > I did a bit of cross-checking, and AFAICT this is a reasonable starting
> > point. emmintrin.h appears to be sufficient for one of my patches that
> > makes use of SSE2
On Wed, Aug 03, 2022 at 12:00:39PM +0700, John Naylor wrote:
> Thanks for checking! Here's a concrete patch for testing.
LGTM
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
11:07:40 +0700
Subject: [PATCH v1] Support SSE2 intrinsics where available
SSE2 vector instructions are part of the spec for the 64-bit x86
architecture. Until now we have relied on the compiler to autovectorize
in some limited situations, but some useful coding idioms can only be
expressed explicit
On Tue, Aug 02, 2022 at 05:22:52PM +0700, John Naylor wrote:
> Given all this, the anti-climax is: it seems we can start with something
> like src/include/port/simd.h with:
>
> #if (defined(__x86_64__) || defined(_M_AMD64))
> #include
> #define USE_SSE2
> #endif
>
> (plus a comment summarizing
without prompting, so to be
safe we'd need to take the latter advice and use .
3. Support for SSE2 intrinsics
This seems to be well-nigh universal AFAICT and doesn't need to be tested
for at configure time. A quick search doesn't turn up anything weird for
Msys or Cygwin. From [2] again, gcc older than