On 2016-05-13 06:34, Samuel Thibault wrote:
Oh, that reminds me, now that we have gsync, we could add a proper
GSCOPE implementation in tls.h, see i386's implementation.
Yes, that's the remaining use of __swtch_pri I talked about.
However, like I mentioned, it needs help from libpthread, so it
Oh, that reminds me, now that we have gsync, we could add a proper
GSCOPE implementation in tls.h, see i386's implementation.
Samuel
Oops, I screwed up the robust low-level lock implementation. Here's an updated
patch with that fix.
I forgot to mention it in my previous message, but I left some global cthreads
types as they were, even though they could be replaced by plain integers now.
I'm not sure if anyone uses them directl
On 2016-05-10 03:12, Samuel Thibault wrote:
Just to make sure: are you building the debian package, or from our
hurd/glibc.git tree? In the debian package at least, the testsuite
should be going on, and give a regression summary: quite a few tests
are
"expected" to fail. tgmath2 is however no
Hello,
Agustina Arzille, on Mon 09 May 2016 22:45:17 -0300, wrote:
> On 05/08/2016 07:42 PM, Samuel Thibault wrote:
> >512M is not so much, perhaps use more as Richard suggested.
>
> I did try that, and got farther than before (Thanks, Richard!). On the other
> hand, glibc's testsuite failed duri
On 05/08/2016 07:42 PM, Samuel Thibault wrote:
512M is not so much, perhaps use more as Richard suggested.
I did try that, and got farther than before (Thanks, Richard!). On the other
hand, glibc's testsuite failed during math/tgmath2, after a crash. The output
was:
(17916) crashed, signal: {
Agustina Arzille writes:
> The GNU C Library is free software; you can redistribute it and/or
> modify it under the terms of the GNU Lesser General Public
> License as published by the Free Software Foundation; either
> - version 2.1 of the License, or (at your option) any later ver
Agustina Arzille, on Fri 06 May 2016 23:19:20 -0300, wrote:
> I run it with "kvm -m 512 -hda debian-hurd-20160325.img", because I had heard
> mixed things about writeback cache. I'll try a build again with that option.
512M is not so much, perhaps use more as Richard suggested.
> >>+/* Gsync flag
On Fri, May 06, 2016 at 11:19:20PM -0300, Agustina Arzille wrote:
> I run it with "kvm -m 512 -hda debian-hurd-20160325.img", because I had heard
> mixed things about writeback cache. I'll try a build again with that option.
The writeback option is only used for performance, but for now, it's
stil
Hello, Samuel
On 05/06/2016 10:36 AM, Samuel Thibault wrote:
I ran into a lot of troubles to compile glibc, mostly because the filesystem
kept freezing and / or crashing.
That's worrying, and surprising to me since buildds keep building stuff
for days without too many issues. How are you run
Hello,
Agustina Arzille, on Thu 05 May 2016 23:02:35 -0300, wrote:
> Here's the first of the patches to replace spin-locks in glibc with locks
> based
> on gnumach's gsync.
Cool :)
> I ran into a lot of troubles to compile glibc, mostly because the filesystem
> kept freezing and / or crashing.
Hello, everyone.
Here's the first of the patches to replace spin-locks in glibc with locks based
on gnumach's gsync.
I ran into a lot of troubles to compile glibc, mostly because the filesystem
kept freezing and / or crashing.
I had to modify several makefiles for a few libs because the new loc
12 matches
Mail list logo
