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 stdio/18542] swscanf vswscanf namespace
Date: Wed, 17 Jun 2015 20:16:00 -0000	[thread overview]
Message-ID: <bug-18542-131-x5QQ1XgFWx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18542-131@http.sourceware.org/bugzilla/>

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

--- 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  45dcd79f6eb37ad4e9e6967f1d459ffc3629eb1f (commit)
      from  eb1fae6a450b3cce5a75c1ed1a734520c56a6457 (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=45dcd79f6eb37ad4e9e6967f1d459ffc3629eb1f

commit 45dcd79f6eb37ad4e9e6967f1d459ffc3629eb1f
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Wed Jun 17 20:15:22 2015 +0000

    Fix swscanf vswscanf namespace (bug 18542).

    swscanf (added in C90 Amendment 1, present in UNIX98) calls vswscanf
    (added in C99, not in C90 Amendment 1 or UNIX98).  This patch fixes
    this by using __vswscanf instead and making vswscanf into a weak
    alias.

    (I intend to add conform/ test support for C90 Amendment 1 - and
    various other standard versions supported by glibc but not yet by
    conform/ tests - at some point, once the results for currently tested
    standards are cleaner.)

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

        [BZ #18542]
        * libio/iovswscanf.c (__vswscanf): Use libc_hidden_def.
        (vswscanf): Use ldbl_weak_alias instead of ldbl_strong_alias
        * include/wchar.h (__vswscanf): Declare.  Use libc_hidden_proto.
        * libio/swscanf.c (__swscanf): Call __vswscanf instead of
        vswscanf.
        * conform/Makefile (test-xfail-UNIX98/wchar.h/linknamespace):
        Remove variable.

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

Summary of changes:
 ChangeLog          |    9 +++++++++
 NEWS               |    2 +-
 conform/Makefile   |    1 -
 include/wchar.h    |    4 ++++
 libio/iovswscanf.c |    3 ++-
 libio/swscanf.c    |    2 +-
 6 files changed, 17 insertions(+), 4 deletions(-)

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


  parent reply	other threads:[~2015-06-17 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-15 22:26 [Bug stdio/18542] New: swscanf vswscanf jsm28 at gcc dot gnu.org
2015-06-15 22:27 ` [Bug stdio/18542] swscanf vswscanf namespace jsm28 at gcc dot gnu.org
2015-06-17 20:16 ` cvs-commit at gcc dot gnu.org [this message]
2015-06-17 20:25 ` 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-18542-131-x5QQ1XgFWx@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).