public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/25824] Abnormal function of strnlen in aarch64
Date: Fri, 15 May 2020 13:22:29 +0000 [thread overview]
Message-ID: <bug-25824-131-qVJsLWNBpG@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-25824-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=25824
Szabolcs Nagy <nsz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |nsz at gcc dot gnu.org
Target Milestone|--- |2.32
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-05-15
--- Comment #7 from Szabolcs Nagy <nsz at gcc dot gnu.org> ---
bigendian strnlen, strcpy (and stpcpy) are fixed for glibc 2.32 in
commit 59b64f9cbbf1e98c6d187873de6c363994aee19d
Author: Lexi Shao <shaolexi@huawei.com>
AuthorDate: 2020-05-15 18:48:59 +0800
aarch64: fix strcpy and strnlen for big-endian [BZ #25824]
falkor and kunpeng920 specific strlen_asimd still needs to be fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-05-15 13:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:25 [Bug libc/25824] New: " zhuyan34 at huawei dot com
2020-04-15 13:32 ` [Bug libc/25824] " schwab@linux-m68k.org
2020-04-15 14:13 ` zhuyan34 at huawei dot com
2020-04-15 14:13 ` zhuyan34 at huawei dot com
2020-04-15 14:35 ` schwab@linux-m68k.org
2020-04-15 16:53 ` wdijkstr at arm dot com
2020-05-11 15:33 ` wdijkstr at arm dot com
2020-05-15 13:22 ` nsz at gcc dot gnu.org [this message]
2020-07-17 14:07 ` cvs-commit at gcc dot gnu.org
2020-07-17 14:56 ` nsz 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-25824-131-qVJsLWNBpG@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).