I haven't had an opportunity to run the test yet (my laptop currently
grinding away building the new release of GCC for m68k) but threads on Linux
when using linuxthreads to my knowledge are almost completely in userland;
linuxthreads uses clone() to create them. If it requires real-time signals
o
I haven't had an opportunity to run the test yet (my laptop currently
grinding away building the new release of GCC for m68k) but threads on Linux
when using linuxthreads to my knowledge are almost completely in userland;
linuxthreads uses clone() to create them. If it requires real-time signals
on
Please find attached the ssh keys and email addresses of the 23 current
m68k buildds. I hope to be able to add 4 more sometime this year.
May 14 or so was the last time any of the m68k porters had access to
buildd.debian.org. I've been maintaining our status manually since then.
I've tried contac
Problem would be rather missing memory barier, or non-atomic operation.
This should be fixable even with 2.5 glibc and linuxthreads.
Do we need a fix in linuxthreads, or the kernel?
I don't know.
The linuxthreads add-on is currently used
by hppa and kfreebsd-* for glibc 2.7.
But the latest e
4 matches
Mail list logo
