From: Jonathan Wakely <jwakely@redhat.com>
To: Nathaniel Shead <nathanieloshead@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Set active union member in constexpr std::string [PR103295]
Date: Fri, 11 Nov 2022 17:12:42 +0000 [thread overview]
Message-ID: <CACb0b4kQEFPGUEHXSeQpeaF8mA-Yo04xtEG6QZ-YN5wK5BzS+g@mail.gmail.com> (raw)
In-Reply-To: <Y24wszWBpJVRv1ma@Thaum.localdomain>
On Fri, 11 Nov 2022 at 11:23, Nathaniel Shead via Libstdc++
<libstdc++@gcc.gnu.org> wrote:
>
> Hi,
>
> Below is a patch to fix std::string in constexpr contexts on Clang. This
> was originally fixed in the commits attached to PR103295, but a later
> commit 98a0d72a seems to have mistakenly undone this.
>
> Tested on x86_64-linux. Verified using clang-14 and clang-15 that the
> fix works. I haven't added anything to the test suite, since this issue
> is only detected by clang.
>
> This is my first time contributing, so please let me know if I've done
> anything wrong or missed something. Thanks!
Thanks for the patch, I'll get this committed today.
The only thing I had to fix was the indentation in the commit log. The
second line of the ChangeLog should be aligned with the * not the text
following it (so indented by a single tab).
>
> Nathaniel
>
> -- >8 --
>
> Clang still complains about using std::string in constexpr contexts due
> to the changes made in commit 98a0d72a. This patch ensures that we set
> the active member of the union as according to [class.union.general] p6.
>
> libstdc++-v3/ChangeLog:
>
> PR libstdc++/103295
> * include/bits/basic_string.h (_M_use_local_data): Set active
> member to _M_local_buf.
>
> Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
> ---
> libstdc++-v3/include/bits/basic_string.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libstdc++-v3/include/bits/basic_string.h b/libstdc++-v3/include/bits/basic_string.h
> index 9c2b57f5a1d..2790fd49b05 100644
> --- a/libstdc++-v3/include/bits/basic_string.h
> +++ b/libstdc++-v3/include/bits/basic_string.h
> @@ -352,8 +352,8 @@ _GLIBCXX_BEGIN_NAMESPACE_CXX11
> {
> #if __cpp_lib_is_constant_evaluated
> if (std::is_constant_evaluated())
> - for (_CharT& __c : _M_local_buf)
> - __c = _CharT();
> + for (size_type i = 0; i <= _S_local_capacity; ++i)
> + _M_local_buf[i] = _CharT();
> #endif
> return _M_local_data();
> }
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-11-11 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 11:23 Nathaniel Shead
2022-11-11 17:12 ` Jonathan Wakely [this message]
2022-11-11 17:55 ` Patrick Palka
2022-11-11 17:59 ` Jonathan Wakely
2022-11-12 0:41 ` Nathaniel Shead
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=CACb0b4kQEFPGUEHXSeQpeaF8mA-Yo04xtEG6QZ-YN5wK5BzS+g@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=nathanieloshead@gmail.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).