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 libc/16885] strcmp() on sparc64 can return wrong result
Date: Thu, 01 May 2014 20:19:00 -0000	[thread overview]
Message-ID: <bug-16885-131-8JdXC0ioST@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-16885-131@http.sourceware.org/bugzilla/>

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

--- Comment #3 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, release/2.15/master has been updated
       via  df137ce8ce4ed11dd4e5efd724c1d249493fb9af (commit)
      from  d9ba4bd3ea5f4c004d8894120e2613a9518a88d6 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=df137ce8ce4ed11dd4e5efd724c1d249493fb9af

commit df137ce8ce4ed11dd4e5efd724c1d249493fb9af
Author: David S. Miller <davem@davemloft.net>
Date:   Wed Apr 30 12:57:51 2014 -0700

    Fix v9/64-bit strcmp when string ends in multiple zero bytes.

        [BZ #16885]
        * sysdeps/sparc/sparc64/strcmp.S: Fix end comparison handling when
        multiple zero bytes exist at the end of a string.
        Reported by Aurelien Jarno <aurelien@aurel32.net>

        * string/test-strcmp.c (check): Add explicit test for situations where
        there are multiple zero bytes after the first.

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog                      |   10 ++++++++++
 string/test-strcmp.c           |   28 ++++++++++++++++++++++++++++
 sysdeps/sparc/sparc64/strcmp.S |   31 +++++++++++++++++++++++++++++++
 3 files changed, 69 insertions(+), 0 deletions(-)

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


  parent reply	other threads:[~2014-05-01 20:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 19:48 [Bug libc/16885] New: " baggett.patrick at gmail dot com
2014-04-29 19:48 ` [Bug libc/16885] " baggett.patrick at gmail dot com
2014-04-30 20:03 ` davem at davemloft dot net
2014-05-01 19:15 ` cvs-commit at gcc dot gnu.org
2014-05-01 20:19 ` cvs-commit at gcc dot gnu.org [this message]
2014-05-01 20:21 ` cvs-commit at gcc dot gnu.org
2014-05-01 20:23 ` cvs-commit at gcc dot gnu.org
2014-05-01 20:24 ` cvs-commit at gcc dot gnu.org
2014-05-01 20:25 ` cvs-commit at gcc dot gnu.org
2014-05-01 21:01 ` davem at davemloft dot net
2014-06-12 19:30 ` fweimer at redhat dot com
2015-01-30  8:47 ` fweimer at redhat dot 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=bug-16885-131-8JdXC0ioST@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).