From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: pthread_key_create bug?
Date: Tue, 8 Jan 2019 20:34:54 +0100 [thread overview]
Message-ID: <20190108193454.GE29911@voyager> (raw)
In-Reply-To: <20190108084310.GD4305@example.net>
On Tue, Jan 08, 2019 at 09:43:10AM +0100, u-uy74@aetey.se wrote:
> On Mon, Jan 07, 2019 at 07:00:18PM -0500, Rich Felker wrote:
> > >
> > > +extern hidden weak void __pthread_key_delete_synccall(void (*f)(void *), void *p);
>
> > musl on the basis (perhaps somewhat dubious) that they're an
> > additional toolchain feature that might cause problems reusing the
> > code in non-ELF contexts (this may affect midipix; I'm not sure).
>
> Thanks. That's no doubt, the less the reliance on toolchain features,
> the easier to use, especially in the ways/areas not known in advance.
>
> Rune
>
Well, what happens on midipix with this patch? Worst case scenario is,
the toolchain doesn't do weak references, and the reference becomes
strong. So that would leave you no worse than the current situation. Or
am I missing the point?
Ciao,
Markus
next prev parent reply other threads:[~2019-01-08 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-06 14:35 Nathaniel Pierce
2019-01-06 14:50 ` A. Wilcox
2019-01-06 16:28 ` Szabolcs Nagy
2019-01-07 2:11 ` Rich Felker
2019-01-07 12:24 ` A. Wilcox
2019-01-07 14:12 ` Rich Felker
2019-01-07 17:13 ` Markus Wichmann
2019-01-08 0:00 ` Rich Felker
2019-01-08 8:43 ` u-uy74
2019-01-08 19:34 ` Markus Wichmann [this message]
2019-01-08 22:40 ` writeonce
2019-01-08 22:10 ` Markus Wichmann
2019-01-08 23:07 ` A. Wilcox
2019-01-09 0:29 ` Rich Felker
2019-01-09 11:45 ` Szabolcs Nagy
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=20190108193454.GE29911@voyager \
--to=nullplan@gmx.net \
--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).