public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/28755] overflow bug in wcsncmp_avx2 and wcsncmp_evex
Date: Thu, 17 Feb 2022 19:22:33 +0000 [thread overview]
Message-ID: <bug-28755-131-fkb2pnag8c@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28755-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28755
--- Comment #13 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The release/2.34/master branch has been updated by H.J. Lu
<hjl@sourceware.org>:
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=04d60ce0f21ffe2a4add148cb37a1942dbad64e2
commit 04d60ce0f21ffe2a4add148cb37a1942dbad64e2
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Thu Feb 17 08:10:35 2022 -0800
string: Add a testcase for wcsncmp with SIZE_MAX [BZ #28755]
Verify that wcsncmp (L("abc"), L("abd"), SIZE_MAX) == 0. The new test
fails without
commit ddf0992cf57a93200e0c782e2a94d0733a5a0b87
Author: Noah Goldstein <goldstein.w.n@gmail.com>
Date: Sun Jan 9 16:02:21 2022 -0600
x86: Fix __wcsncmp_avx2 in strcmp-avx2.S [BZ# 28755]
and
commit 7e08db3359c86c94918feb33a1182cd0ff3bb10b
Author: Noah Goldstein <goldstein.w.n@gmail.com>
Date: Sun Jan 9 16:02:28 2022 -0600
x86: Fix __wcsncmp_evex in strcmp-evex.S [BZ# 28755]
This is for BZ #28755.
Reviewed-by: Sunil K Pandey <skpgkp2@gmail.com>
(cherry picked from commit aa5a720056d37cf24924c138a3dbe6dace98e97c)
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-17 19:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 10:30 [Bug string/28755] New: " goldstein.w.n at gmail dot com
2022-01-09 14:07 ` [Bug string/28755] " hjl.tools at gmail dot com
2022-01-10 0:29 ` goldstein.w.n at gmail dot com
2022-01-11 3:07 ` goldstein.w.n at gmail dot com
2022-01-27 4:24 ` cvs-commit at gcc dot gnu.org
2022-01-27 4:58 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:14 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:29 ` cvs-commit at gcc dot gnu.org
2022-01-27 13:33 ` cvs-commit at gcc dot gnu.org
2022-01-27 15:28 ` cvs-commit at gcc dot gnu.org
2022-01-27 16:12 ` cvs-commit at gcc dot gnu.org
2022-01-27 16:14 ` hjl.tools at gmail dot com
2022-02-17 19:04 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:14 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-17 19:27 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:32 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:40 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:43 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:48 ` cvs-commit at gcc dot gnu.org
2022-02-17 19:52 ` cvs-commit at gcc dot gnu.org
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=bug-28755-131-fkb2pnag8c@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).