public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: "孙世龙 sunshilong via Libc-help" <libc-help@sourceware.org>
Subject: Re: How to verify some macro is available for a specific version of GLIBC that is installed on my PC?
Date: Sun, 16 Aug 2020 19:00:40 +0800	[thread overview]
Message-ID: <CAAvDm6Y66Vh08aDbG1LF2MjwKYyUxYcyp-xtMoJOA5=gw-YMqQ@mail.gmail.com> (raw)
In-Reply-To: <87d03qkinm.fsf@mid.deneb.enyo.de>

Thank you for your clarification.

>You can read the glibc source code.
No other methods? Maybe it's meaningful(or faster) when verifying when
a specific macro is first introduced then reading each version source
code.

>__MALLOC_HOOK_VOLATILE is an internal macro and should only be used
>within glibc itself.  It can go away at any time.
Do you indicate that the said macro could not be found in the headers of GLIBC?

Best Regards
Sunshilong

On Sun, Aug 16, 2020 at 6:08 PM Florian Weimer <fw@deneb.enyo.de> wrote:
>
> * 孙世龙 sunshilong via Libc-help:
>
> > How can I verify some macro is available for a specific version of
> > GLIBC that is installed on my PC, e.g:__MALLOC_HOOK_VOLATILE?
>
> You can read the glibc source code.
>
> __MALLOC_HOOK_VOLATILE is an internal macro and should only be used
> within glibc itself.  It can go away at any time.

  reply	other threads:[~2020-08-16 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-16 10:02 孙世龙 sunshilong
2020-08-16 10:08 ` Florian Weimer
2020-08-16 11:00   ` 孙世龙 sunshilong [this message]
2020-08-16 11:18     ` Florian Weimer

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='CAAvDm6Y66Vh08aDbG1LF2MjwKYyUxYcyp-xtMoJOA5=gw-YMqQ@mail.gmail.com' \
    --to=sunshilong369@gmail.com \
    --cc=fw@deneb.enyo.de \
    --cc=libc-help@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).