Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Hi Louis, Thank you for a contact, at last. Yes, Thomas created a repo for gccgo in 2013?. Sorry I cannot find it right now. Nevertheless, I'd really appreciate a repo where I can submit my patches to, and for you to work from, Samuel/Thomas? (FYI: The patches for gccgo are already included in the

RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

I apologize for any annoyances my inquiries has caused up to this point, you are correct in that I should have googled to check the archive to see the archives of bug-hurd, but the only relevant result for GNU/Hurd gccgo brings me here: https://www.gnu.org/software/hurd/open_issues/gccgo.html T

RE: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

One more thing: I see it is now CC’d, but would he be able to see the previous messages, or should I ask directly there? From: Samuel Thibault Sent: Saturday, March 4, 2017 6:02 PM To: Louis Jenkins Cc: summer-of-c...@gnu.org

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

On Sun, 2017-03-05 at 00:44 +0100, Samuel Thibault wrote: > Louis Jenkins, on sam. 04 mars 2017 23:16:30 +, wrote: > > One more thing: I see it is now CC’d, but would he be able to see > > the previous > > messages, or should I ask directly there? > > Google for "bug-hurd", and you'll find the

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Louis Jenkins, on sam. 04 mars 2017 23:16:30 +, wrote: > One more thing: I see it is now CC’d, but would he be able to see the previous > messages, or should I ask directly there? Google for "bug-hurd", and you'll find the mailing list archives. Samuel

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Hello, Louis Jenkins, on sam. 04 mars 2017 22:38:06 +, wrote: > As for Svante Signell, I was googling his name a bit and the most relevant I > could find was for [1]svante.sign...@gmail.com would that be his appropriate > email address, or is there a way to search or communicate through the ma

Re: [GSoC 2017] Porting Google Go (GCC: gccgo) - Questions and Concerns

Louis Jenkins, on ven. 03 mars 2017 20:20:20 +, wrote: > However, again, before I delve further I would like to know first if it is > still active, or can potentially be restarted. So, assuming that this is about porting Go to the GNU/Hurd system, you need to be aware that some work has been d

Re: [PATCH 2/2] Rewrite gsync so that it works with remote tasks v2

Samuel Thibault, on sam. 04 mars 2017 23:35:58 +0100, wrote: > AIUI, the problem is that rpctrace uses only one thread to do the > tracing, (thus related with Brent's "multithread rpctrace to avoid deadlocks in the kernel" patch)

Re: [PATCH 2/2] Rewrite gsync so that it works with remote tasks v2

Hello, Did you actually try with rpctrace? It seems to be breaking it. For instance: #include #include pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER; void *f(void *foo) { pthread_mutex_lock(&mutex); sleep(1); pthread_mutex_unlock(&mutex); return NULL; } int

Re: [PATCH 1/2] Implement basic sleeping locks for gnumach v2

Applied, thanks! Samuel

Re: [PATCH 2/2] Rewrite gsync so that it works with remote tasks v2

Samuel Thibault, on sam. 04 mars 2017 22:54:39 +0100, wrote: > Samuel Thibault, on sam. 04 mars 2017 22:45:08 +0100, wrote: > > Agustina Arzille, on mer. 01 févr. 2017 12:32:53 -0300, wrote: > > > /* Look for a key that matches. We take advantage of the fact > > > * that the entries are sorted to

Re: [PATCH 2/2] Rewrite gsync so that it works with remote tasks v2

Samuel Thibault, on sam. 04 mars 2017 22:45:08 +0100, wrote: > Agustina Arzille, on mer. 01 févr. 2017 12:32:53 -0300, wrote: > > /* Look for a key that matches. We take advantage of the fact > > * that the entries are sorted to break out of the loop as > > * early as possible. */ > > Do we real

Re: [PATCH 2/2] Rewrite gsync so that it works with remote tasks v2

Hello, While reviewing the patch, I was thinking (this is actually unrelated, just a TODO for later): Agustina Arzille, on mer. 01 févr. 2017 12:32:53 -0300, wrote: > /* Look for a key that matches. We take advantage of the fact > * that the entries are sorted to break out of the loop as > * ea

Re: Patch for gsync and sleeping locks

Hello, BTW, did you try to stress this? e.g. by running a patched gnumach kernel, and run e.g. a glibc build in userland. Samuel

Re: Failed with output: Hydra job gnu:glibc-hurd:hurd_patches on x86_64-linux

Samuel Thibault, on sam. 04 mars 2017 15:30:26 +0100, wrote: > Hydra Build Daemon, on sam. 04 mars 2017 14:41:15 +0100, wrote: > > The status of Hydra job ‘gnu:glibc-hurd:hurd_patches’ (on x86_64-linux) has > > changed from "Success" to "Failed with output". For details, see > > Ooh, that's very

Re: Failed with output: Hydra job gnu:glibc-hurd:hurd_patches on x86_64-linux

Hello, Hydra Build Daemon, on sam. 04 mars 2017 14:41:15 +0100, wrote: > The status of Hydra job ‘gnu:glibc-hurd:hurd_patches’ (on x86_64-linux) has > changed from "Success" to "Failed with output". For details, see Ooh, that's very cool automatic output :) However, the log links on this page