From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: Dynamic linker refactoring
Date: Sun, 22 Jan 2012 13:45:00 +0100 [thread overview]
Message-ID: <c07b7aa089e00bb08f896a84b8257e01@exys.org> (raw)
In-Reply-To: <20120122043047.GN132@brightrain.aerifal.cx>
Ah now i see what you're doing there, thanks for the explanation.
> 2. Include the vdso-linking code directly in the functions (like
> clock_gettime) that might want vdso code.
Perfect. I like the kernel-code-in-userspace hack, but doing it through
a dso seemed not very well thought out.
Your idea sounds a lot cleaner.
prev parent reply other threads:[~2012-01-22 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 1:05 Rich Felker
2012-01-21 12:19 ` aep
2012-01-22 4:30 ` Rich Felker
2012-01-22 12:45 ` aep [this message]
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=c07b7aa089e00bb08f896a84b8257e01@exys.org \
--to=aep@exys.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).