From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>,
Libc-stable Mailing List <libc-stable@sourceware.org>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] Initialize wchar_t string with wmemset [BZ #27655]
Date: Thu, 27 Jan 2022 09:06:03 -0800 [thread overview]
Message-ID: <CAMe9rOpst-6OjdoBi41Je7MbxBDigkYKENKNRZKRi0g7sb6XvQ@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOohkO06iCdC1UTwkvhw6i4HZOEzZT1zEi4NvED5+6qwOw@mail.gmail.com>
On Sat, Mar 27, 2021 at 10:56 AM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Sat, Mar 27, 2021 at 10:52 AM Florian Weimer <fw@deneb.enyo.de> wrote:
> >
> > * H. J. Lu:
> >
> > > Subject: [PATCH v2] Initialize wchar_t string with wmemset [BZ #27655]
> > >
> > > Use wmemset to initialize wchar_t string.
> > > ---
> > > string/test-strnlen.c | 4 +++-
> > > 1 file changed, 3 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/string/test-strnlen.c b/string/test-strnlen.c
> > > index a49d93afa2..b98dc10a56 100644
> > > --- a/string/test-strnlen.c
> > > +++ b/string/test-strnlen.c
> > > @@ -27,6 +27,7 @@
> > >
> > > #ifndef WIDE
> > > # define STRNLEN strnlen
> > > +# define MEMSET memset
> > > # define CHAR char
> > > # define BIG_CHAR CHAR_MAX
> > > # define MIDDLE_CHAR 127
> > > @@ -34,6 +35,7 @@
> > > #else
> > > # include <wchar.h>
> > > # define STRNLEN wcsnlen
> > > +# define MEMSET wmemset
> > > # define CHAR wchar_t
> > > # define BIG_CHAR WCHAR_MAX
> > > # define MIDDLE_CHAR 1121
> > > @@ -153,7 +155,7 @@ do_page_tests (void)
> > > size_t last_offset = (page_size / sizeof (CHAR)) - 1;
> > >
> > > CHAR *s = (CHAR *) buf2;
> > > - memset (s, 65, (last_offset - 1));
> > > + MEMSET (s, 65, (last_offset - 1));
> > > s[last_offset] = 0;
> > >
> > > /* Place short strings ending at page boundary. */
> >
> > Patch looks good. Please change the commit message to mention that
> > this changes just a test.
>
> I changed the commit subject to
>
> test-strnlen.c: Initialize wchar_t string with wmemset [BZ #27655]
>
> --
> H.J.
I am backporting this to release branches.
--
H.J.
parent reply other threads:[~2022-01-27 17:06 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAMe9rOohkO06iCdC1UTwkvhw6i4HZOEzZT1zEi4NvED5+6qwOw@mail.gmail.com>]
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=CAMe9rOpst-6OjdoBi41Je7MbxBDigkYKENKNRZKRi0g7sb6XvQ@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=fw@deneb.enyo.de \
--cc=libc-alpha@sourceware.org \
--cc=libc-stable@sourceware.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).