public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mkretz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107929] std::experimental::simd needs to be reimplemented with GCC's vector extension
Date: Thu, 01 Dec 2022 10:07:42 +0000	[thread overview]
Message-ID: <bug-107929-4-Mmpqo9j3x6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107929-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107929

--- Comment #4 from Matthias Kretz (Vir) <mkretz at gcc dot gnu.org> ---
I agree that compilation speed is a problem. However,

1. GCC's vector extensions are not sufficient (especially for use of AVX-512
masks)

2. I see 0.6s difference between calling `g++ -O2 -march=skylake` on an empty
file vs. a file that #includes <immintrin.h>. Whereas #include
<experimental/simd> takes about 2.7s.

  parent reply	other threads:[~2022-12-01 10:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-30  3:52 [Bug libstdc++/107929] New: " unlvsur at live dot com
2022-11-30  3:54 ` [Bug libstdc++/107929] " unlvsur at live dot com
2022-11-30 20:16 ` mkretz at gcc dot gnu.org
2022-11-30 22:00 ` unlvsur at live dot com
2022-12-01 10:07 ` mkretz at gcc dot gnu.org [this message]
2022-12-01 18:52 ` unlvsur at live dot com

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=bug-107929-4-Mmpqo9j3x6@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).