public inbox for glibc-bugs-regex@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs-regex@sourceware.org
Subject: [Bug regex/18496] regcomp wcrtomb namespace
Date: Fri, 05 Jun 2015 21:32:00 -0000	[thread overview]
Message-ID: <bug-18496-132-vRtX5m5yyg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18496-132@http.sourceware.org/bugzilla/>

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

--- 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  a5f0adb39b3a029b3fcd1b0d879eb45d9bd742cd (commit)
      from  007f2dd1228a4b21b10756c696876babb8cf86cd (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=a5f0adb39b3a029b3fcd1b0d879eb45d9bd742cd

commit a5f0adb39b3a029b3fcd1b0d879eb45d9bd742cd
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Fri Jun 5 21:31:39 2015 +0000

    Fix regex wcrtomb namespace (bug 18496).

    The regex code brings in references to wcrtomb, which isn't in all the
    standards that contain regex.  This patch makes it call __wcrtomb
    instead (in fact some places already called __wcrtomb, so this patch
    makes it internally consistent about which name is used).

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

        [BZ #18496]
        * posix/regex_internal.c (build_wcs_upper_buffer): Call __wcrtomb
        instead of wcrtomb.

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

Summary of changes:
 ChangeLog              |    4 ++++
 NEWS                   |    2 +-
 posix/regex_internal.c |    4 ++--
 3 files changed, 7 insertions(+), 3 deletions(-)

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


  reply	other threads:[~2015-06-05 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-05 20:16 [Bug regex/18496] New: " jsm28 at gcc dot gnu.org
2015-06-05 21:32 ` cvs-commit at gcc dot gnu.org [this message]
2015-06-05 21:33 ` [Bug regex/18496] " 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-18496-132-vRtX5m5yyg@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs-regex@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).