[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190215190312.GD23599@brightrain.aerifal.cx>
Date: Fri, 15 Feb 2019 14:03:12 -0500
From: Rich Felker <dalias@...c.org>
To: musl@...ts.openwall.com
Subject: Re: Bugs found while working on global thread list
3. Not exactly a bug, but found looking at cruft/bloat in struct
pthread: the start function pointer and argument are reused in a
hackish way for timer threads. There are actually a lot of ugly hacks
in the whole way SIGEV_THREAD timers are implemented, that could be
eliminated by either waiting for the signal (rather than handling it)
or doing away with use of signals and kernel timers entirely for
SIGEV_THREAD, and instead implementing it all in userspace with
clock_nanosleep.
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
