From: Jonathan Wakely <jwakely@redhat.com>
To: Deev Patel <pateldeev@nevada.unr.edu>
Cc: gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] libstdc++: Add missing constexpr specifier and function overloads
Date: Mon, 24 Jul 2023 21:15:12 +0100 [thread overview]
Message-ID: <ZL7b0NphdC6i+itA@redhat.com> (raw)
In-Reply-To: <CACJEya+wn7RxPr5t=MYr5Xedh7q4q=CfwiA=qPP7mk4uRq7zNw@mail.gmail.com>
On 23/07/23 20:28 -0700, Deev Patel wrote:
>Hi,
>
>A couple of virtual functions in the libstdc++ format header are marked
>constexpr in the base class, but not in the derived class. This was causing
>build failures when trying to compile latest gcc libstd with clang 16 using
>c++20. Adding the constexpr specifier resolves the issue.
>
>2023-07-23 Deev Patel <pateldeev@nevada.unr.edu>
>
> * include/std/format: Add missing constexpr specifiers on function overloads
Thanks for the patch, I'll test and push it.
N.B. libstdc++ patches should be CC'd to the libstdc++ mailing list,
or I won't see them (and rely on somebody bringing it to my
attention).
>---
> libstdc++-v3/include/std/format | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/libstdc++-v3/include/std/format b/libstdc++-v3/include/std/format
>index 9710bff3c03..0c6069b2681 100644
>--- a/libstdc++-v3/include/std/format
>+++ b/libstdc++-v3/include/std/format
>@@ -3554,14 +3554,14 @@ namespace __format
>
> using iterator = typename _Scanner<_CharT>::iterator;
>
>- void
>+ constexpr void
> _M_on_chars(iterator __last) override
> {
> basic_string_view<_CharT> __str(this->begin(), __last);
> _M_fc.advance_to(__format::__write(_M_fc.out(), __str));
> }
>
>- void
>+ constexpr void
> _M_format_arg(size_t __id) override
> {
> using _Context = basic_format_context<_Out, _CharT>;
prev parent reply other threads:[~2023-07-24 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 3:28 Deev Patel
2023-07-24 20:15 ` Jonathan Wakely [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=ZL7b0NphdC6i+itA@redhat.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=pateldeev@nevada.unr.edu \
/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).