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/18522] ecvt_r, fcvt_r namespace
Date: Fri, 12 Jun 2015 10:12:00 -0000	[thread overview]
Message-ID: <bug-18522-131-eQyNQwSFlH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18522-131@http.sourceware.org/bugzilla/>

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

--- 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  498c1f6a7c7f7b634d02e740f15789cf68820a54 (commit)
      from  9acacaa02f3b75fddc07a56f3d848df45281a5de (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=498c1f6a7c7f7b634d02e740f15789cf68820a54

commit 498c1f6a7c7f7b634d02e740f15789cf68820a54
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Fri Jun 12 10:11:35 2015 +0000

    Fix ecvt_r, fcvt_r namespace (bug 18522).

    The functions ecvt, fcvt and gcvt, in some standards, bring in
    references to ecvt_r and fcvt_r, which aren't in any of those
    standards.  The calls are correctly to __ecvt_r and __fcvt_r, but then
    the names ecvt_r and fcvt_r are defined as strong aliases; this patch
    changes them to weak aliases.

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

        [BZ #18522]
        * misc/efgcvt_r.c
        [LONG_DOUBLE_COMPAT (libc, GLIBC_2_0) && !LONG_DOUBLE_CVT]
        (cvt_symbol): Use weak_alias instead of strong_alias.
        [LONG_DOUBLE_COMPAT (libc, GLIBC_2_0)] (cvt_symbol): Likewise.
        * conform/Makefile (test-xfail-XPG4/stdlib.h/linknamespace):
        Remove variable.
        (test-xfail-UNIX98/stdlib.h/linknamespace): Likewise.
        (test-xfail-XOPEN2K/stdlib.h/linknamespace): Likewise.

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

Summary of changes:
 ChangeLog        |   10 ++++++++++
 NEWS             |    2 +-
 conform/Makefile |    3 ---
 misc/efgcvt_r.c  |    4 ++--
 4 files changed, 13 insertions(+), 6 deletions(-)

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


  reply	other threads:[~2015-06-12 10:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-11 21:53 [Bug libc/18522] New: " jsm28 at gcc dot gnu.org
2015-06-12 10:12 ` cvs-commit at gcc dot gnu.org [this message]
2015-06-12 10:13 ` [Bug libc/18522] " 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-18522-131-eQyNQwSFlH@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).