public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "goldstein.w.n at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug string/29839] [2.37 Regression] Wrong result in function __strncpy_avx2: 75 != 0
Date: Thu, 01 Dec 2022 22:42:41 +0000	[thread overview]
Message-ID: <bug-29839-131-7Og6BnEbiB@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29839-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29839

--- Comment #2 from Noah Goldstein <goldstein.w.n at gmail dot com> ---
(In reply to H.J. Lu from comment #1)
> I am testing this:
> 
> diff --git a/sysdeps/x86_64/multiarch/strncpy-avx2.S
> b/sysdeps/x86_64/multiarch/strncpy-avx2.S
> index e9afd8fbed..3e6350ce4a 100644
> --- a/sysdeps/x86_64/multiarch/strncpy-avx2.S
> +++ b/sysdeps/x86_64/multiarch/strncpy-avx2.S
> @@ -52,6 +52,10 @@
>  
>    .section SECTION(.text), "ax", @progbits
>  ENTRY(STRNCPY)
> +# ifdef __ILP32__
> +  /* Clear the upper 32 bits.  */
> +  movl  %edx, %edx
> +# endif
>    /* Filter zero length strings and very long strings.  Zero
>       length strings just return, very long strings are handled by
>       just running rep stos{b|l} to zero set (which will almost

evex version will need the same treatment (assuming that works).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2022-12-01 22:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-01 22:24 [Bug string/29839] New: " hjl.tools at gmail dot com
2022-12-01 22:31 ` [Bug string/29839] " hjl.tools at gmail dot com
2022-12-01 22:42 ` goldstein.w.n at gmail dot com [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=bug-29839-131-7Og6BnEbiB@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).