From: Marc Glisse <marc.glisse@inria.fr>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Matthias Kretz <m.kretz@gsi.de>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Add missing constexpr to simd
Date: Mon, 22 May 2023 22:56:57 +0200 (CEST) [thread overview]
Message-ID: <11b29c5b-e25d-18aa-16d0-1780c215c9ba@inria.fr> (raw)
In-Reply-To: <CACb0b4=jKUKnUbr8iMVRTQ1CkYtWj7DPR03Z3rk3y_CJSXcx2w@mail.gmail.com>
On Mon, 22 May 2023, Jonathan Wakely via Libstdc++ wrote:
>> * subscripting vector builtins is not allowed in constant expressions
>
> Is that just because nobody made it work (yet)?
Yes.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101651 and others.
>> * if the implementation would otherwise call SIMD intrinsics/builtins
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517 and others.
Makes sense to work around them for now.
--
Marc Glisse
prev parent reply other threads:[~2023-05-22 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 15:36 Matthias Kretz
2023-05-22 16:25 ` Jonathan Wakely
2023-05-22 20:27 ` Matthias Kretz
2023-05-22 20:51 ` Jonathan Wakely
2023-05-23 7:30 ` [committed] " Matthias Kretz
2023-05-22 20:56 ` Marc Glisse [this message]
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=11b29c5b-e25d-18aa-16d0-1780c215c9ba@inria.fr \
--to=marc.glisse@inria.fr \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=m.kretz@gsi.de \
/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).