From: Andreas Schwab <schwab@suse.de>
To: Zack Weinberg <zackw@panix.com>
Cc: Richard Henderson <rth@twiddle.net>,
libc-alpha@sourceware.org, fweimer@redhat.com
Subject: Re: [PATCH 0/3] explicit_bzero v5
Date: Wed, 16 Nov 2016 14:58:00 -0000 [thread overview]
Message-ID: <mvmwpg34gkj.fsf@hawking.suse.de> (raw)
In-Reply-To: <500cef03-f7e2-f152-660d-438b08ac1f45@panix.com> (Zack Weinberg's message of "Wed, 16 Nov 2016 09:45:17 -0500")
On Nov 16 2016, Zack Weinberg <zackw@panix.com> wrote:
> This doesn't fully resolve the question in my head, though. The case
> we're discussing is an impl-namespace symbol __explicit_bzero, which is
> functionally identical to a public symbol explicit_bzero, and not
> expected ever to change its behavior. It exists, as far as I
> understand, _solely_ so that uses of this symbol in libcrypt.so will
> resolve to the definition in libc.so even if other objects in the link
> interpose on the public symbol.
It's a public symbol, so it gets a public version. It does not matter
whether the reference is created explicitly or implicitly.
Andreas.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2016-11-16 14:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 15:55 Zack Weinberg
2016-11-15 15:55 ` [PATCH 1/3] New string function explicit_bzero (from OpenBSD) Zack Weinberg
2016-11-15 15:55 ` [PATCH 2/3] Add fortification and inline optimization of explicit_bzero Zack Weinberg
2016-11-15 15:55 ` [PATCH 3/3] Use explicit_bzero where appropriate Zack Weinberg
2016-11-16 18:38 ` [PATCH 1/3] New string function explicit_bzero (from OpenBSD) Michael Kerrisk (man-pages)
2016-11-15 16:20 ` [PATCH 0/3] explicit_bzero v5 Paul Eggert
2016-11-15 17:46 ` Zack Weinberg
2016-11-15 18:02 ` Paul Eggert
2016-11-15 18:42 ` Florian Weimer
2016-11-15 18:54 ` Zack Weinberg
2016-11-15 19:35 ` Paul Eggert
2016-11-16 14:56 ` Zack Weinberg
2016-11-16 21:38 ` Paul Eggert
2016-11-16 18:34 ` Michael Kerrisk (man-pages)
2016-11-15 19:35 ` Paul Eggert
2016-11-16 14:58 ` Zack Weinberg
2016-11-15 21:12 ` Richard Henderson
2016-11-16 14:45 ` Zack Weinberg
2016-11-16 14:58 ` Andreas Schwab [this message]
2016-11-16 15:00 ` Zack Weinberg
2016-11-16 15:09 ` Andreas Schwab
2016-11-16 15:14 ` Zack Weinberg
2016-11-16 15:22 ` Andreas Schwab
2016-11-16 20:06 ` Richard Henderson
2016-11-16 2:03 ` Joseph Myers
2016-11-16 15:06 ` Zack Weinberg
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=mvmwpg34gkj.fsf@hawking.suse.de \
--to=schwab@suse.de \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rth@twiddle.net \
--cc=zackw@panix.com \
/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).