Hello!
On Tue, Jun 23, 2009 at 12:05:42AM +0200, I wrote:
> On Sun, Apr 12, 2009 at 05:32:12PM +0200, I wrote:
> > When linking the pthread tests against a libpthread built (with Samuel's
> > TLS patches) from CVS HEAD (or any of the Viengoos branches, for that
> > matter) I always get this:
> >
Thomas Schwinge, le Tue 23 Jun 2009 00:05:42 +0200, a écrit :
> I also published a patch in master-fix_inline to fix an inlining problem
> that I discovered when using Debian unstable's gcc-4.4. Neal, Samuel, is
> this fine for master?
Should be, yes.
> Already some weeks ago, I published master
Hello!
On Sun, Apr 12, 2009 at 05:32:12PM +0200, I wrote:
> When linking the pthread tests against a libpthread built (with Samuel's
> TLS patches) from CVS HEAD (or any of the Viengoos branches, for that
> matter) I always get this:
>
> $ ./test-1
> test-1: ../../HEAD/libpthread/sysdeps/
Thomas Schwinge, le Sun 12 Apr 2009 17:32:12 +0200, a écrit :
>__mach_port_destroy (__mach_task_self (),
> thread->wakeupmsg.msgh_remote_port);
> +
> + thread->have_kernel_resources = 0;
> }
Mmm, I do not like setting have_kernel_resources being set to 0 in
pthread_threa
Hello!
On Sun, Apr 12, 2009 at 08:37:40PM +0200, Samuel Thibault wrote:
> Thomas Schwinge, le Sun 12 Apr 2009 17:32:12 +0200, a écrit :
> > PPS: While digging through the libpthread code I wondered whether for the
> > Hurd servers cthreads to pthread migration PTHREAD_THREADS_MAX being
> > defined
Thomas Schwinge, le Sun 12 Apr 2009 17:32:12 +0200, a écrit :
> PPS: While digging through the libpthread code I wondered whether for the
> Hurd servers cthreads to pthread migration PTHREAD_THREADS_MAX being
> defined to 64 might be too small for some heavily multi-threaded Hurd
> servers?
Where
Hello!
When linking the pthread tests against a libpthread built (with Samuel's
TLS patches) from CVS HEAD (or any of the Viengoos branches, for that
matter) I always get this:
$ ./test-1
test-1: ../../HEAD/libpthread/sysdeps/mach/hurd/i386/pt-setup.c:103:
__pthread_setup: Unexpected
