From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Make 16-bit std::subtract_with_carry_engine work [PR107466]
Date: Mon, 28 Nov 2022 15:28:08 +0000 [thread overview]
Message-ID: <CACb0b4k6bvbj5pk0-TaRTdgcKVOj-oUqdyMP-VKS4SrTdvJvKw@mail.gmail.com> (raw)
In-Reply-To: <20221128152003.41709-1-jwakely@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 269 bytes --]
On Mon, 28 Nov 2022 at 15:20, Jonathan Wakely via Libstdc++ <
libstdc++@gcc.gnu.org> wrote:
> Tested x86_64-linux. Pushed to trunk.
>
I didn't notice until my mailer flagged it that this commit has a non-ASCII
character. Fixed by the attached patch, pushed to trunk.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 1113 bytes --]
commit c775e2b81fca39f366040d423e3e44f4abecf753
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Mon Nov 28 15:21:52 2022
libstdc++: Replace non-ASCII character in comment
This has an unnecessary UTF-8 non-breaking space.
libstdc++-v3/ChangeLog:
* testsuite/26_numerics/random/subtract_with_carry_engine/cons/lwg3809.cc:
Replace non-ASCII character.
diff --git a/libstdc++-v3/testsuite/26_numerics/random/subtract_with_carry_engine/cons/lwg3809.cc b/libstdc++-v3/testsuite/26_numerics/random/subtract_with_carry_engine/cons/lwg3809.cc
index 21f246b8dc0..d91ee7448f6 100644
--- a/libstdc++-v3/testsuite/26_numerics/random/subtract_with_carry_engine/cons/lwg3809.cc
+++ b/libstdc++-v3/testsuite/26_numerics/random/subtract_with_carry_engine/cons/lwg3809.cc
@@ -3,7 +3,7 @@
#include <testsuite_hooks.h>
// LWG 3809. Is std::subtract_with_carry_engine<uint16_t> supposed to work?
-// PR 107466 - invalid -Wnarrowing error with std::subtract_with_carry_engine
+// PR 107466 - invalid -Wnarrowing error with std::subtract_with_carry_engine
int main()
{
prev parent reply other threads:[~2022-11-28 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-28 15:20 Jonathan Wakely
2022-11-28 15:28 ` 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=CACb0b4k6bvbj5pk0-TaRTdgcKVOj-oUqdyMP-VKS4SrTdvJvKw@mail.gmail.com \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).