[Bug libc/17719] New: [x86_64] memrchr namespace

[Bug libc/17719] New: [x86_64] memrchr namespace

[jsm28 at gcc dot gnu.org]

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

            Bug ID: 17719
           Summary: [x86_64] memrchr namespace
           Product: glibc
           Version: 2.21
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: jsm28 at gcc dot gnu.org
                CC: drepper.fsp at gmail dot com

On x86_64, memrchr (not a standard function) is defined as a strong symbol,
instead of a weak alias of __memrchr as on other architectures.  This results
in linknamespace test failures from the use of __memrchr from dirname.  (Not a
conformance issue because of the mem* reservation, but contrary to glibc
conventions.)

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

[Bug libc/17719] [x86_64] memrchr namespace

[cvs-commit at gcc dot gnu.org]

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

--- Comment #1 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, master has been updated
       via  380292ba8b97c82a8ede3ed35f6a3c42b7b47466 (commit)
      from  9a44d530c464d081e925b1c1af2b8bbe6e7b3207 (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=380292ba8b97c82a8ede3ed35f6a3c42b7b47466

commit 380292ba8b97c82a8ede3ed35f6a3c42b7b47466
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Dec 16 18:31:31 2014 +0000

    Fix x86_64 memrchr namespace (bug 17719).

    On x86_64, memrchr (not a standard function) is defined as a strong
    symbol, instead of a weak alias of __memrchr as on other
    architectures.  This results in linknamespace test failures from the
    use of __memrchr from dirname.  (Not a conformance issue because of
    the mem* reservation, but contrary to glibc conventions.)  This patch
    makes x86_64 follow other architectures by defining memrchr as a weak
    alias.

    Tested for x86_64 (testsuite, and that disassembly of installed shared
    libraries is unchanged by the patch).

        [BZ #17719]
        * sysdeps/x86_64/memrchr.S (memrchr): Rename to __memrchr and
        define as weak alias of __memrchr.
        (__memrchr): Do not define as strong alias of memrchr.
        * conform/Makefile (test-xfail-XPG4/libgen.h/linknamespace):
        Remove variable.
        (test-xfail-UNIX98/libgen.h/linknamespace): Likewise.
        (test-xfail-XOPEN2K/libgen.h/linknamespace): Likewise.
        (test-xfail-XOPEN2K8/libgen.h/linknamespace): Likewise.

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

Summary of changes:
 ChangeLog                |   10 ++++++++++
 NEWS                     |    2 +-
 conform/Makefile         |    4 ----
 sysdeps/x86_64/memrchr.S |    6 +++---
 4 files changed, 14 insertions(+), 8 deletions(-)

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

[Bug libc/17719] [x86_64] memrchr namespace

[jsm28 at gcc dot gnu.org]

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

Joseph Myers <jsm28 at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #2 from Joseph Myers <jsm28 at gcc dot gnu.org> ---
Fixed for 2.21.

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