Christoph Egger christ...@debian.org writes:
Petr Salinger petr.salin...@seznam.cz writes:
Updated version of FBTL (NPTL like) glibc is available from experimental.
I've been running the experimental libc now for several days on my
notebook without any trouble!
Oh and FWIW LXDE seems to
Btw, I don't have time to do this right now, but it might be a good
idea to try the testsuites for ruby, perl and python (and possibly
others). They tend to break very easily on thread-related problems (as
I'm sure you remember ;-)).
During development, I used glib2.0 and ruby1.9.1 as secondary
Hi.
Updated version of FBTL (NPTL like) glibc is available from experimental.
Thanks to Aurelien.
Petr
--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
2013/7/17 Petr Salinger petr.salin...@seznam.cz:
Hi.
Updated version of FBTL (NPTL like) glibc is available from experimental.
Nice!
Btw, I don't have time to do this right now, but it might be a good
idea to try the testsuites for ruby, perl and python (and possibly
others). They tend to
Hi Petr,
Are you sure about this?
/* TID of the helper thread. */
-extern __lwpid_t __helper_tid attribute_hidden;
+extern pid_t __helper_tid attribute_hidden;
(in kernel-posix-timers.h and timer_routines.c)
lwpid_t happens to match pid_t but AFAICT they're supposed to be
different things.
/* TID of the helper thread. */
-extern __lwpid_t __helper_tid attribute_hidden;
+extern pid_t __helper_tid attribute_hidden;
(in kernel-posix-timers.h and timer_routines.c)
lwpid_t happens to match pid_t but AFAICT they're supposed to be
different things. Nothing prevents upstream from
2013/7/13 Petr Salinger petr.salin...@seznam.cz:
In theory yes, but in practice, both pid and tid are limited
to range 1 .. (2^30-1) due to other constrains in kernel.
Moreover, even currently the TID value is in some places
(thr_exit, thr_self) passed as long.
See
Btw, I'm running your NPTL on my desktop (I force-fed it into a Wheezy
system) and all seems fine so far. Tried iceweasel and icedove.
Thanks for testing.
What's your deployment plan? Is this being uploaded to experimental,
or directly to sid?
I am not a DD, I cannot upload anywhere.
I
2013/7/13 Petr Salinger petr.salin...@seznam.cz:
I am not a DD, I cannot upload anywhere.
I believe it is ready as-is for experimental.
Please, could you reupload it ?
Sorry I can't. You need to request this to the eglibc maintainers. May
I suggest submitting a wishlist item to the BTS to keep
2013/7/10 Petr Salinger petr.salin...@seznam.cz:
As you might know, we are still using linuxthreads based
pthread implementation.
I would like to ask you to test NPTL like pthread implementation.
Please find it for both kfreebsd-* at
http://asdfasdf.debian.net/~salinger/eglibc.fbtl/
You're
2013/7/11 Robert Millan r...@debian.org:
When I ported pthread timers, I also ported them to NPTL at the same
time, but (obviously) couldn't test them at the time.
This wasn't accurate. What I mean is that they were originally for
NPTL/Linux, and I ported them to LT/kFreeBSD in two steps,
When I ported pthread timers, I also ported them to NPTL at the same
time, but (obviously) couldn't test them at the time. Did you test
those and/or merge them into your port? They're in
ports/sysdeps/unix/bsd/bsd4.4/kfreebsd/nptl/ (in sysdeps.diff).
I did it in a different way, first changes
Hi.
As you might know, we are still using linuxthreads based
pthread implementation.
I would like to ask you to test NPTL like pthread implementation.
Please find it for both kfreebsd-* at
http://asdfasdf.debian.net/~salinger/eglibc.fbtl/
Cheers
Petr
--
To UNSUBSCRIBE,
13 matches
Mail list logo
