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/14132] Get rid of INTDEF/INTUSE and *_internal aliases
Date: Tue, 21 Oct 2014 23:12:00 -0000	[thread overview]
Message-ID: <bug-14132-131-q9AFk0Dzsb@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14132-131@http.sourceware.org/bugzilla/>

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

--- Comment #5 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  a13d0d745ca3ea5e80506db7de0498d74d44a5b7 (commit)
      from  f05e73f660d5cc3a72b46047c829ccf5e096c88b (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=a13d0d745ca3ea5e80506db7de0498d74d44a5b7

commit a13d0d745ca3ea5e80506db7de0498d74d44a5b7
Author: Joseph Myers <joseph@codesourcery.com>
Date:   Tue Oct 21 23:11:49 2014 +0000

    Don't use INTDEF with __ldexpf (bug 14132).

    Continuing the removal of the obsolete INTDEF / INTUSE mechanism, this
    patch removes the use of INTDEF for __ldexpf.  As far as I can tell,
    the resulting alias is completely unused.

    Tested for x86_64 that stripped installed shared libraries are
    unchanged by this patch.

        [BZ #14132]
        * math/s_ldexpf.c (__ldexpf): Do not use INTDEF.

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

Summary of changes:
 ChangeLog       |    5 +++++
 math/s_ldexpf.c |    1 -
 2 files changed, 5 insertions(+), 1 deletions(-)

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


  parent reply	other threads:[~2014-10-21 23:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 20:18 [Bug libc/14132] New: " roland at gnu dot org
2012-05-29 15:59 ` [Bug libc/14132] " polacek at redhat dot com
2014-06-19 16:07 ` fweimer at redhat dot com
2014-10-08 23:20 ` cvs-commit at gcc dot gnu.org
2014-10-09  1:12 ` cvs-commit at gcc dot gnu.org
2014-10-09 11:23 ` cvs-commit at gcc dot gnu.org
2014-10-10 11:14 ` cvs-commit at gcc dot gnu.org
2014-10-21 23:12 ` cvs-commit at gcc dot gnu.org [this message]
2014-10-23 21:44 ` cvs-commit at gcc dot gnu.org
2014-10-28 17:14 ` cvs-commit at gcc dot gnu.org
2014-10-29 18:29 ` fweimer at redhat dot com
2014-11-04 17:40 ` cvs-commit at gcc dot gnu.org
2014-11-04 23:27 ` cvs-commit at gcc dot gnu.org
2014-11-05  1:03 ` cvs-commit at gcc dot gnu.org
2014-11-05 23:36 ` cvs-commit at gcc dot gnu.org
2014-11-05 23:39 ` 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-14132-131-q9AFk0Dzsb@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).