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/31756] write_profiling is only in libc.a
Date: Wed, 22 May 2024 13:13:27 +0000	[thread overview]
Message-ID: <bug-31756-131-49TTMG72ma@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31756-131@http.sourceware.org/bugzilla/>

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

--- Comment #1 from Sourceware Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by H.J. Lu <hjl@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=6d3b523eb54198d15af6e042054912cf9f5210de

commit 6d3b523eb54198d15af6e042054912cf9f5210de
Author: H.J. Lu <hjl.tools@gmail.com>
Date:   Sun May 19 18:46:53 2024 -0700

    Define write_profiling functions only in profile library [BZ #31756]

    libc.so doesn't use nor export write_profiling functions.  There is no
    point to define them in libc.so nor in libc.a.  Fix BZ #31756 by defining
    them only in profile library.

    Signed-off-by: H.J. Lu <hjl.tools@gmail.com>
    Reviewed-by: Adhemerval Zanella  <adhemerval.zanella@linaro.org>

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

  reply	other threads:[~2024-05-22 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-19 22:38 [Bug libc/31756] New: " hjl.tools at gmail dot com
2024-05-22 13:13 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-24 12:49 ` [Bug libc/31756] " hjl.tools at gmail dot com

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-31756-131-49TTMG72ma@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).