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/17719] [x86_64] memrchr namespace
Date: Tue, 16 Dec 2014 18:32:00 -0000	[thread overview]
Message-ID: <bug-17719-131-yG6CSyOivH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17719-131@http.sourceware.org/bugzilla/>

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.


  reply	other threads:[~2014-12-16 18:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 17:55 [Bug libc/17719] New: " jsm28 at gcc dot gnu.org
2014-12-16 18:32 ` cvs-commit at gcc dot gnu.org [this message]
2014-12-16 18:33 ` [Bug libc/17719] " jsm28 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-17719-131-yG6CSyOivH@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).