public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: Matthias Kretz <m.kretz@gsi.de>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Add missing constexpr to simd
Date: Mon, 22 May 2023 21:51:49 +0100	[thread overview]
Message-ID: <CACb0b4nkM_Xv6MubNJ3N4t6YvbKrSu-oNUzH8eJFXxzGJfj0nA@mail.gmail.com> (raw)
In-Reply-To: <13129784.rMLUfLXkoz@minbar>

[-- Attachment #1: Type: text/plain, Size: 2511 bytes --]

On Mon, 22 May 2023 at 21:27, Matthias Kretz <m.kretz@gsi.de> wrote:

> On Monday, 22 May 2023 18:25:15 CEST Jonathan Wakely wrote:
> > I note that using if (not __builtin_constant_evaluated()) will fail if
> > compiled with -fno-operator-names, which is why we don't use 'not',
> 'and',
> > etc. elsewhere in libstdc++. I don't know if (or why) anybody uses that
> > option though, so I don't think you need to hange anything in stdx::simd.
>
> Ah, I just recently convinced myself that "operator-names" are more
> readable
> (=> easier to maintain).


I tend to agree, but every time I decide to start using them some testcases
start to fail and I remember why we don't use them :-(



> But OTOH a mix isn't necessarily better. I'm fine
> with keeping it consistent.
>
> > > * subscripting vector builtins is not allowed in constant expressions
> >
> > Is that just because nobody made it work (yet)?
>
> That is a good question. I guess I should open a PR.
>
> > * if the implementation needs/uses memcpy
> >
> > > * if the implementation would otherwise call SIMD intrinsics/builtins
> >
> > The indentation looks off here and in the _M_set member function
> following
> > it:
>
> Yes. I had to put an #if between an else and an if. Looks like this:
>
>   else
> #ifdef _GLIBCXX_SIMD_USE_ALIASING_LOADS
>     if (not __builtin_is_constant_evaluated())
>     return reinterpret_cast<const __may_alias<_Tp>*>(this)[__i];
>   else
> #endif
>     if constexpr (__is_scalar_abi<_Abi0>())
>
>
Ah yes, so the if is indented two spaces from the else above it.
What looks wrong to me is that the return is the at the same indentation as
the if controlling it.



> Should the `if` be aligned to the `else` instead?
>

How about moving the two else tokens?

 #ifdef _GLIBCXX_SIMD_USE_ALIASING_LOADS
   else if (not __builtin_is_constant_evaluated())
     return reinterpret_cast<const __may_alias<_Tp>*>(this)[__i];
 #endif
   else if constexpr (__is_scalar_abi<_Abi0>())

I think that avoids the issue.



>
> > Are the copyright years on
> > testsuite/experimental/simd/pr109261_constexpr_simd.cc correct, or just
> > copy&paste?
>
> Right, copy&paste. Should I simply remove the complete header?
>
>
You could do. I don't think there's much in that test that's novel or worth
asserting copyright over - but if you disagree and want to assign whatever
is copyrightable to the FSF, keep the header but fix the years. Either way
is fine by me.

OK for trunk and backports, with the comments above suitably resolved.

  reply	other threads:[~2023-05-22 20:52 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 [this message]
2023-05-23  7:30       ` [committed] " Matthias Kretz
2023-05-22 20:56   ` Marc Glisse

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=CACb0b4nkM_Xv6MubNJ3N4t6YvbKrSu-oNUzH8eJFXxzGJfj0nA@mail.gmail.com \
    --to=jwakely@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --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).