Re: [PATCH gcc] Hurd x86_64: add unwind support for signal trampoline code

2024-02-29 Thread Samuel Thibault
lavio Cruz Reviewed-by: Samuel Thibault Thanks!! > --- > libgcc/config/i386/gnu-unwind.h | 97 - > 1 file changed, 94 insertions(+), 3 deletions(-) > > diff --git a/libgcc/config/i386/gnu-unwind.h b/libgcc/config/i386/gnu-unwind.h > index 0751b55

Re: hurd: Ad default-pie and static-pie support

2023-11-27 Thread Samuel Thibault
Thomas Schwinge, le lun. 27 nov. 2023 15:52:02 +0100, a ecrit: > On 2023-10-28T21:20:39+0200, Samuel Thibault wrote: > > This fixes the Hurd spec in the default-pie case, and adds static-pie > > support. > > I understand that your change does work for you as-i

Re: hurd: Add multilib paths for gnu-x86_64

2023-11-27 Thread Samuel Thibault
Hello, Thomas Schwinge, le lun. 27 nov. 2023 15:48:33 +0100, a ecrit: > On 2023-10-28T21:19:59+0200, Samuel Thibault wrote: > > This is essentially based on t-linux64 version. > > Yes, but isn't the overall setup diverged from GNU/Linux? Not sure what you mean exactl

[PATCH,resend] hurd: Ad default-pie and static-pie support

2023-10-28 Thread Samuel Thibault
This fixes the Hurd spec in the default-pie case, and adds static-pie support. gcc/ChangeLog: * gcc/config/i386/gnu.h: Use PIE_SPEC, add static-pie case. * gcc/config/i386/gnu64.h: Use PIE_SPEC, add static-pie case. diff --git a/gcc/config/i386/gnu.h b/gcc/config/i386/gnu.h

[PATCH,resend] hurd: Add multilib paths for gnu-x86_64

2023-10-28 Thread Samuel Thibault
We need the multilib paths in gcc to find e.g. glibc crt files on Debian. This is essentially based on t-linux64 version. gcc/ChangeLog: * gcc/config/i386/t-gnu64: New file. * gcc/config.gcc [x86_64-*-gnu*): Add i386/t-gnu64 to tmake_file. diff --git a/gcc/config.gcc

Re: [PATCH] hurd: Add multilib paths for gnu-x86_64

2023-05-06 Thread Samuel Thibault via Gcc-patches
(and it'd be useful to have it backported to the 13 branch) Samuel Thibault, le sam. 06 mai 2023 13:50:36 +0200, a ecrit: > We need the multilib paths in gcc to find e.g. glibc crt files on > Debian. This is essentially based on t-linux64 version. > > gcc/ChangeLog: > >

[PATCH] hurd: Ad default-pie and static-pie support

2023-05-06 Thread Samuel Thibault via Gcc-patches
This fixes the Hurd spec in the default-pie case, and adds static-pie support. gcc/ChangeLog: * gcc/config/i386/gnu.h: Use PIE_SPEC, add static-pie case. * gcc/config/i386/gnu64.h: Use PIE_SPEC, add static-pie case. diff --git a/gcc/config/i386/gnu.h b/gcc/config/i386/gnu.h

[PATCH] hurd: Add multilib paths for gnu-x86_64

2023-05-06 Thread Samuel Thibault via Gcc-patches
We need the multilib paths in gcc to find e.g. glibc crt files on Debian. This is essentially based on t-linux64 version. gcc/ChangeLog: * gcc/config/i386/t-gnu64: New file. * gcc/config.gcc [x86_64-*-gnu*): Add i386/t-gnu64 to tmake_file. diff --git a/gcc/config.gcc

[PATCH]: Fix static-pie on Hurd target

2022-10-23 Thread Samuel Thibault via Gcc-patches
When linking with -static-pie, we need to use rcrt0.o (and grcrt0.o for -pg). Also, set static:crt0.o before pie:Scrt1.o, otherwise -static -pie fails to link with Scrt1.o due to missing _DYNAMIC symbol. Also, -static-pie needs crtbeginS.o (otherwise it contains a relocation in read-only .text).

[PATCHv2] libstdc++: Mark pieces of gnu-linux/os_support.h linux-specific

2022-10-07 Thread Samuel Thibault via Gcc-patches
This is notably needed because in glibc 2.34, the move of pthread functions into libc.so happened for Linux only, not GNU/Hurd. The pthread_self() function can also always be used fine as it is on GNU/Hurd. libstdc++-v3/ChangeLog: * config/os/gnu-linux/os_defines.h [!__linux__]

Re: [PATCH] libstdc++: Introduce GNU/Hurd-specific libstdc++ os-defines.h

2022-10-07 Thread Samuel Thibault via Gcc-patches
t noticed that. > On 29/08/22 02:30 +0200, Samuel Thibault wrote: > > This is notably needed because in glibc 2.34, the move of pthread functions > > into libc.so happened for Linux only, not GNU/Hurd. > > > > The pthread_self() function can also always be used fine as it

Re: [PATCH] libstdc++: Introduce GNU/Hurd-specific libstdc++ os-defines.h

2022-09-17 Thread Samuel Thibault via Gcc-patches
Ping? Samuel Thibault, le lun. 29 août 2022 02:30:40 +0200, a ecrit: > This is notably needed because in glibc 2.34, the move of pthread functions > into libc.so happened for Linux only, not GNU/Hurd. > > The pthread_self() function can also always be used fine as it is. >

[PATCH] libstdc++: Introduce GNU/Hurd-specific libstdc++ os-defines.h

2022-08-28 Thread Samuel Thibault via Gcc-patches
100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,11 @@ +2022-08-28 Samuel Thibault + + * config/os/gnu/os_defines.h: New file. + * config/os/gnu/ctype_base.h: New file. + * config/os/gnu/ctype_configure_char.cc: New file. + * config/os/gnu

Re: [PATCH] Hurd: Enable ifunc by default

2021-01-18 Thread Samuel Thibault via Gcc-patches
Hello, Joseph Myers, le lun. 18 janv. 2021 20:05:44 +, a ecrit: > On Wed, 13 Jan 2021, Thomas Schwinge wrote: > > Thanks (and sorry for the delay), pushed "Hurd: Enable ifunc by default" > > to master branch in commit e9cb89b936f831a02318d45fc4ddb06f7be55ae4, and > > cherry-picked into

Re: [PATCHv2] hurd: libgcc unwinding over signal trampolines with SIGINFO

2021-01-10 Thread Samuel Thibault via Gcc-patches
Ping? Samuel Thibault, le lun. 21 déc. 2020 15:36:30 +0100, a ecrit: When the application sets SA_SIGINFO, the signal trampoline parameters are different to follow POSIX. libgcc/ * config/i386/gnu-unwind.h (x86_gnu_fallback_frame_state): Add the posix siginfo case to struct handler_args. Detect

Re: [PATCH] Hurd: Enable ifunc by default

2021-01-10 Thread Samuel Thibault via Gcc-patches
Ping? Samuel Thibault, le dim. 08 nov. 2020 23:52:51 +0100, a ecrit: > The binutils bugs seem to have been fixed. > > 2020-11-08 Samuel Thibault > > gcc/ > * config.gcc: Enable default_gnu_indirect_function in *-*-gnu* > target (but not *-*-kfreebsd*-g

Re: [PATCH] libtool.m4: update GNU/Hurd test from upstream

2021-01-05 Thread Samuel Thibault via Gcc-patches
Jeff Law, le mar. 05 janv. 2021 16:04:45 -0700, a ecrit: > Thanks.  Installed. Thanks! Samuel

Re: [PATCH] libtool.m4: update GNU/Hurd test from upstream

2021-01-04 Thread Samuel Thibault via Gcc-patches
Hello, Jeff Law, le lun. 04 janv. 2021 13:29:53 -0700, a ecrit: > On 12/23/20 6:12 PM, Samuel Thibault wrote: > > In upstream libtool, 47a889a4ca20 ("Improve GNU/Hurd support.") fixed > > detection of shlibpath_overrides_runpath, thus avoiding unnecessary r

[PATCH] libtool.m4: update GNU/Hurd test from upstream

2020-12-23 Thread Samuel Thibault
In upstream libtool, 47a889a4ca20 ("Improve GNU/Hurd support.") fixed detection of shlibpath_overrides_runpath, thus avoiding unnecessary relink. This backports it. ChangeLog: * libtool.m4: Match gnu* along other GNU systems. * libffi/configure: Re-generate. *

[PATCHv2] hurd: libgcc unwinding over signal trampolines with SIGINFO

2020-12-21 Thread Samuel Thibault via Gcc-patches
When the application sets SA_SIGINFO, the signal trampoline parameters are different to follow POSIX. libgcc/ * config/i386/gnu-unwind.h (x86_gnu_fallback_frame_state): Add the posix siginfo case to struct handler_args. Detect between legacy and siginfo from the second parameter, which is a small

Re: [PATCH] hurd: libgcc unwinding over signal trampolines with SIGINFO

2020-12-21 Thread Samuel Thibault via Gcc-patches
Jessica Clarke, le lun. 21 déc. 2020 14:21:39 +, a ecrit: > On 21 Dec 2020, at 14:09, Samuel Thibault wrote: > > @@ -75,29 +86,52 @@ x86_gnu_fallback_frame_state > > return _URC_END_OF_STACK; > > > > handler_args = context->cfa; > > - scp = handler_

[PATCH] hurd: libgcc unwinding over signal trampolines with SIGINFO

2020-12-21 Thread Samuel Thibault via Gcc-patches
When the application sets SA_SIGINFO, the signal trampoline parameters are different to follow POSIX. libgcc/ * config/i386/gnu-unwind.h (x86_gnu_fallback_frame_state): Add the posix siginfo case to struct handler_args. Detect between legacy and siginfo from the second parameter, which is a small

Re: [PATCH] Hurd: Enable ifunc by default

2020-12-20 Thread Samuel Thibault via Gcc-patches
Almudena Garcia, le lun. 21 déc. 2020 01:05:29 +0100, a ecrit: > What do you need exactly? I need gcc people to apply it. > How can we test It? The answer would be lengthy. Basically recompile gcc with it, write or find a program that uses it, and check that it works. But I have already done

Re: [PATCH] Hurd: Enable ifunc by default

2020-12-20 Thread Samuel Thibault via Gcc-patches
Ping? Samuel Thibault, le dim. 08 nov. 2020 23:52:51 +0100, a ecrit: > The binutils bugs seem to have been fixed. > > 2020-11-08 Samuel Thibault > > gcc/ > * config.gcc: Enable default_gnu_indirect_function in *-*-gnu* > target (but not *-*-kfreebsd*-g

Re: [PATCH] Hurd: Enable ifunc by default

2020-12-04 Thread Samuel Thibault via Gcc-patches
Ping? Samuel Thibault, le dim. 08 nov. 2020 23:52:51 +0100, a ecrit: > The binutils bugs seem to have been fixed. > > 2020-11-08 Samuel Thibault > > gcc/ > * config.gcc: Enable default_gnu_indirect_function in *-*-gnu* > target (but not *-*-kfreebsd*-g

Re: [PATCH] Hurd: Enable ifunc by default

2020-11-21 Thread Samuel Thibault via Gcc-patches
Ping? I was able to pass glibc's complete ifunc tests with no problem. Samuel Samuel Thibault, le dim. 08 nov. 2020 23:52:51 +0100, a ecrit: > The binutils bugs seem to have been fixed. > > 2020-11-08 Samuel Thibault > > gcc/ > * config.gcc: Enable default_gnu

[PATCH] Hurd: Enable ifunc by default

2020-11-08 Thread Samuel Thibault
The binutils bugs seem to have been fixed. 2020-11-08 Samuel Thibault gcc/ * config.gcc: Enable default_gnu_indirect_function in *-*-gnu* target (but not *-*-kfreebsd*-gnu | *-*-kopensolaris*-gnu). --- gcc/config.gcc | 4 +++- 1 file changed, 3 insertions(+), 1

Re: [PATCH] hurd: libgcc unwinding support over signal trampolines

2020-06-08 Thread Samuel Thibault
Samuel Thibault, le lun. 08 juin 2020 13:36:55 +0200, a ecrit: > Thomas Schwinge, le lun. 08 juin 2020 12:15:12 +0200, a ecrit: > > Which GCC branches would you like this on? > > Ideally it's be backported to gcc 9 and 10, so that it lands naturally > in the Debian packa

Re: [PATCH] hurd: libgcc unwinding support over signal trampolines

2020-06-08 Thread Samuel Thibault
Thomas Schwinge, le lun. 08 juin 2020 12:15:12 +0200, a ecrit: > I'm not currently set up to test this, but I'll assume you have. Sure :) > Which GCC branches would you like this on? Ideally it's be backported to gcc 9 and 10, so that it lands naturally in the Debian packages without having to

Re: [PATCH] hurd: libgcc unwinding support over signal trampolines

2020-06-06 Thread Samuel Thibault
Hello, Any news on this? Samuel Samuel Thibault, le ven. 29 mai 2020 13:46:50 +0200, a ecrit: > Hello, > > libgcc is currently missing the support for unwinding over signal > trampolines on GNU/Hurd. The attached patch implements it. > > Samuel > hurd: libgcc unwindin

[PATCH] hurd: libgcc unwinding support over signal trampolines

2020-05-29 Thread Samuel Thibault
unwinding support for GNU Hurd: x86. + Copyright (C) 2020 Free Software Foundation, Inc. + Contributed by Samuel Thibault + +This file is part of GCC. + +GCC is free software; you can redistribute it and/or modify +it under the terms of the GNU General Public License as published by +the Free Software F

Re: [PATCH] Updated patches for the port of gccgo to GNU/Hurd

2019-02-11 Thread Samuel Thibault
Svante Signell, le lun. 11 févr. 2019 12:10:21 +0100, a ecrit: > WCONTINUED is not defined, I assume that WIFCONTINUED is not supported. > > From waitpid(2): > WCONTINUED (since Linux 2.6.10) >also return if a stopped child has been resumed by delivery of SIGCONT. > > @Samuel: more info?

Re: Update: Hurd port for gcc-7 go : 7.3.0-8+ for glibc 2.26+

2018-03-10 Thread Samuel Thibault
Hello, Svante Signell, on sam. 10 mars 2018 19:33:35 +0100, wrote: > Attached is the updated patch, src_libgo_build.diff, to build gccgo properly > on > Debian GNU/Hurd on gcc-7 (7-7.3.0-{8,9,10}) again after the update of glibc to > 2.26+ I have updated the gcc-7 package in Debian, thanks!

Re: Hurd port for gcc-7 go PATCH 1-3(15)

2017-11-19 Thread Samuel Thibault
Hello, Svante Signell, on lun. 06 nov. 2017 16:36:39 +0100, wrote: > Another issue is that /proc/self/exe has to return an absolute path for the > built program go-7 to execute properly. This is solved by a pending patch for > glibc in Debian and will be available in the next upload of

Re: Hurd port for gcc go PATCH 1-4(23)

2016-12-18 Thread Samuel Thibault
Samuel Thibault, on Mon 19 Dec 2016 00:25:35 +0100, wrote: > as the attached patch does, which should really be applied or done > any other way. Or rather this patch, which makes it more like the test above. Matthias, I'm committing this to Debian's gcc-6, along the other go patches from

Re: Hurd port for gcc go PATCH 1-4(23)

2016-12-18 Thread Samuel Thibault
Hello, Svante Signell, on Fri 25 Nov 2016 20:57:26 +0100, wrote: > Another more annoying gnumch/hurd/glibc bug is that the > built program go (go-6 in Debian) gets killed when executed from the > shell vi path, but not when issued directly: /usr/bin/go-6 works fine. >  go-6 > Segmentation fault

Re: Hurd port for gcc go PATCH 1-4(23)

2016-12-07 Thread Samuel Thibault
Svante Signell, on Wed 07 Dec 2016 15:32:31 +0100, wrote: > On Wed, 2016-12-07 at 15:08 +0100, Samuel Thibault wrote: > > Ok, but then I'd say move the function which change to a separate file, > > so that the other functions are kept shared. > > Otherwise it'll be tedious

Re: Hurd port for gcc go PATCH 1-4(23)

2016-12-07 Thread Samuel Thibault
Svante Signell, on Wed 07 Dec 2016 14:52:35 +0100, wrote: > Since go does not have a preprocessor allowing conditional code paths this is > how it should be done (and as I did): > http://blog.ralch.com/tutorial/golang-conditional-compilation/ Ok, but then I'd say move the function which change to

Re: Hurd port for gcc go PATCH 1-4(23)

2016-11-27 Thread Samuel Thibault
Svante Signell, on Sun 27 Nov 2016 18:17:17 +0100, wrote: > On Sun, 2016-11-27 at 18:02 +0100, Samuel Thibault wrote: > > > But as you wish, an updated patch is attached. > > > >  _Bool > >  Continued (uint32_t *w) > >  { > > +#ifndef WCONTINUED

Re: Hurd port for gcc go PATCH 1-4(23)

2016-11-27 Thread Samuel Thibault
Hello, Svante Signell, on Sun 27 Nov 2016 17:33:52 +0100, wrote: > > > Index: gcc-6-6.2.1-4.1/src/libgo/go/syscall/wait.c > > > === > > > --- gcc-6-6.2.1-4.1.orig/src/libgo/go/syscall/wait.c > > > +++

Re: Please include ada-hurd.diff upstream (try2)

2016-05-04 Thread Samuel Thibault
Svante Signell, on Wed 04 May 2016 23:25:28 +0200, wrote: > On Wed, 2016-05-04 at 23:06 +0200, Samuel Thibault wrote: > > Svante Signell, on Wed 04 May 2016 19:43:27 +0200, wrote: > > > May I comment on Debian way of apt-get source gcc-*: Doing that > > > does > >

Re: Please include ada-hurd.diff upstream (try2)

2016-05-04 Thread Samuel Thibault
Svante Signell, on Wed 04 May 2016 19:43:27 +0200, wrote: > May I comment on Debian way of apt-get source gcc-*: Doing that does > not unpack the sources, neither does it apply the patches, you have to > unpack and patch before you can change sources and update patches. Iv'e > patched the sources

Re: Please include ada-hurd.diff upstream (try2)

2016-05-04 Thread Samuel Thibault
Samuel Thibault, on Wed 04 May 2016 17:29:48 +0200, wrote: > The gcc-6 build failed. I see that one of the change is: > > - -- From: /usr/include/unistd.h __getpagesize or getpagesize?? > - function Get_Page_Size return int; > + -- From: /usr/include/i386-gnu/bits/shm.

Re: Please include ada-hurd.diff upstream (try2)

2016-05-04 Thread Samuel Thibault
Hello Svante, The gcc-6 build failed. I see that one of the change is: - -- From: /usr/include/unistd.h __getpagesize or getpagesize?? - function Get_Page_Size return int; + -- From: /usr/include/i386-gnu/bits/shm.h __getpagesize or getpagesize?? + function Get_Page_Size return size_t;

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2016-03-29 Thread Samuel Thibault
Hello, Thomas Schwinge, on Tue 29 Mar 2016 23:19:09 +0200, wrote: > On Wed, 24 Feb 2016 23:46:36 +0100, I wrote: > > On Sat, 19 Sep 2015 14:00:23 +0200, Samuel Thibault > > <samuel.thiba...@gnu.org> wrote: > > > On Linux, -p and -pg do not make gcc link against libc

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2016-02-25 Thread Samuel Thibault
Samuel Thibault, on Thu 25 Feb 2016 00:18:21 +0100, wrote: > Thomas Schwinge, on Wed 24 Feb 2016 23:46:36 +0100, wrote: > > I guess getting -D_REENTRANT for -pthread won't do us any harm? > > It won't. (Actually we've been using this in Debian for a long time). Samuel

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2016-02-24 Thread Samuel Thibault
Thomas Schwinge, on Wed 24 Feb 2016 23:46:36 +0100, wrote: > I guess getting -D_REENTRANT for -pthread won't do us any harm? It won't. > > --- gcc/config/i386/gnu.h.orig 2015-09-17 21:41:13.0 + > > +++ gcc/config/i386/gnu.h 2015-09-17 23:03:57.0 + > > @@ -27,11

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2016-01-13 Thread Samuel Thibault
Ping? Samuel Thibault, on Sun 11 Oct 2015 20:29:10 +0200, wrote: > Ping? > > (I don't have commit access) > > Samuel Thibault, le Sat 19 Sep 2015 14:00:23 +0200, a écrit : > > On Linux, -p and -pg do not make gcc link against libc_p.a, only > > -profile does (as docu

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2015-10-11 Thread Samuel Thibault
Ping? (I don't have commit access) Samuel Thibault, le Sat 19 Sep 2015 14:00:23 +0200, a écrit : > On Linux, -p and -pg do not make gcc link against libc_p.a, only > -profile does (as documented in r11246), and thus people expect -p > and -pg to work without libc_p.a installed (it is

Re: [PATCH] hurd: align -p and -pg behavior on Linux

2015-09-28 Thread Samuel Thibault
Ping? Samuel Thibault, le Sat 19 Sep 2015 14:00:23 +0200, a écrit : > On Linux, -p and -pg do not make gcc link against libc_p.a, only > -profile does (as documented in r11246), and thus people expect -p > and -pg to work without libc_p.a installed (it is actually even not > availa

[PATCH] hurd: align -p and -pg behavior on Linux

2015-09-19 Thread Samuel Thibault
On Linux, -p and -pg do not make gcc link against libc_p.a, only -profile does (as documented in r11246), and thus people expect -p and -pg to work without libc_p.a installed (it is actually even not available any more in Debian). We should thus rather make the Hurd port do the same to avoid

Re: patch8.diff updated Was: Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 09:47:08 +0200, a écrit : +# Special treatment of EWOULDBLOCK for GNU/Hurd +# /usr/include/bits/errno.h: #define EWOULDBLOCK EAGAIN +if egrep 'define EWOULDBLOCK EAGAIN' gen-sysinfo.go /dev/null 21; then + egrep '^const EWOULDBLOCK =

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 09:49:59 +0200, a écrit : Thomas and Samuel: It looks like upstream don't accept patches unless a Hurd port maintainer commits to it. What's the use of all this job? Well, simply to keep the changes working. That is not surprising at all. (Of course it can

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 10:20:16 +0200, a écrit : On Wed, 2014-05-21 at 10:03 +0200, Samuel Thibault wrote: Svante Signell, le Wed 21 May 2014 09:49:59 +0200, a écrit : Thomas and Samuel: It looks like upstream don't accept patches unless a Hurd port maintainer commits

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Arnaud Charlet, le Wed 21 May 2014 10:33:31 +0200, a écrit : I think the majority of work has bee done, Now that patch will change slightly for every missing feature added to Hurd. Then it's all good, it's a matter of what I said above. Don't forget also the part where general

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 10:40:37 +0200, a écrit : What kind of person do you have to be to be accepted, a GNU/Hurd developer or a GNU/Ada developer having a gnu.org account? Nothing special, just like for contributing to any opensource project; just someone who checks from

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 10:44:54 +0200, a écrit : On Wed, 2014-05-21 at 10:33 +0200, Arnaud Charlet wrote: I think the majority of work has bee done, Now that patch will change slightly for every missing feature added to Hurd. Then it's all good, it's a matter of what I

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 11:22:44 +0200, a écrit : On Wed, 2014-05-21 at 10:47 +0200, Samuel Thibault wrote: Svante Signell, le Wed 21 May 2014 10:40:37 +0200, a écrit : What kind of person do you have to be to be accepted, a GNU/Hurd developer or a GNU/Ada developer having

Re: [PATCH] Add support for GNU/Hurd in gnat-4.9

2014-05-21 Thread Samuel Thibault
Svante Signell, le Wed 21 May 2014 11:42:30 +0200, a écrit : On Wed, 2014-05-21 at 11:27 +0200, Samuel Thibault wrote: Guaranteeing long term support *is* about taking up the work of checking periodically that the port works fine. If anybody does it, then it's fine. If nobody does

Re: patch8.diff updated Was: Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-20 Thread Samuel Thibault
Svante Signell, le Fri 16 May 2014 10:03:05 +0200, a écrit : is used in gcc-4.9-4.9.0/src/libgo/go/net/fd_unix.go: func dupCloseOnExec(fd int) (newfd int, err error) { if atomic.LoadInt32(tryDupCloexec) == 1 syscall.F_DUPFD_CLOEXEC!=0 { r0, _, e1 := syscall.Syscall(syscall.SYS_FCNTL,

Re: Hurd port for gcc go PATCH 7-9 (9)

2014-05-06 Thread Samuel Thibault
Svante Signell, le Tue 06 May 2014 10:58:38 +0200, a écrit : The patch for st_dev by Thomas Schwinge was not liked by Samuel Uh? I said “These should be fine, however.” and “a sed rule can't hurt even if there is no occurrence...” So just keep that precise part back as it was, no need for

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-06 Thread Samuel Thibault
Just to explicitly ask for it: Svante Signell, le Tue 06 May 2014 10:06:49 +0200, a écrit : For some (yet) unknown reason all libgo tests fails with a segfault when run in the build tree: make, sh or something else, the test commands are rather hard to track. Doesn't that dump a core? Do you

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-06 Thread Samuel Thibault
Svante Signell, le Tue 06 May 2014 15:05:20 +0200, a écrit : On Tue, 2014-05-06 at 14:51 +0200, Samuel Thibault wrote: Just to explicitly ask for it: Svante Signell, le Tue 06 May 2014 10:06:49 +0200, a écrit : For some (yet) unknown reason all libgo tests fails with a segfault when

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-06 Thread Samuel Thibault
Svante Signell, le Tue 06 May 2014 15:25:38 +0200, a écrit : On Tue, 2014-05-06 at 15:07 +0200, Samuel Thibault wrote: Svante Signell, le Tue 06 May 2014 15:05:20 +0200, a écrit : On Tue, 2014-05-06 at 14:51 +0200, Samuel Thibault wrote: Just to explicitly ask for it: Svante

Re: Hurd port for gcc go PATCH 7-9 (9)

2014-05-06 Thread Samuel Thibault
Svante Signell, le Tue 06 May 2014 14:13:54 +0200, a écrit : +# Special treatment of EWOULDBLOCK for GNU/Hurd +# /usr/include/bits/errno.h: #define EWOULDBLOCK EAGAIN +egrep '^const EWOULDBLOCK = Errno(_EWOULDBLOCK)' ${OUT} | \ +sed -i.bak -e 's/_EWOULDBLOCK/_EAGAIN/' ${OUT} +

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Svante Signell, le Fri 02 May 2014 10:18:12 +0200, a écrit : Thread 4 (Thread 1205.4): #0 0x019977b7 in _hurd_intr_rpc_msg_in_trap () at intr-msg.c:132 err = optimized out err = optimized out user_option = 3 user_timeout = 48 m = 0x532370

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Svante Signell, le Fri 02 May 2014 10:03:23 +0200, a écrit : On Fri, 2014-05-02 at 00:45 +0200, Samuel Thibault wrote: Hello, Svante Signell, le Thu 24 Apr 2014 10:39:10 +0200, a écrit : - Without split stack enabled around 70 libgo tests pass and 50 fails, most of them

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Justus Winter, le Sat 26 Apr 2014 08:53:08 +0200, a écrit : task130(pid1182)-vm_map (0 49880 0 1133--160(pid1182) 0 1 5 7 1) = 0 2453504 We map that somewhere. task130(pid1182)-mach_port_deallocate (pn{ 25}) = 0 Deallocate the port. Again, for some strange reason 133 == pn{ 25}.

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Svante Signell, le Fri 02 May 2014 10:18:12 +0200, a écrit : task130(pid1182)-vm_allocate (33562796 8364 0) = 0x3 ((os/kern) no space available) task130(pid1182)-vm_allocate (33571160 8364 0) = 0 33570816 While inspecting this, I realized this is from __pthread_stack_alloc, the only caller

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Samuel Thibault, le Fri 02 May 2014 11:57:53 +0200, a écrit : So we just need to fix guardsize in our libpthread. (And I'll have a look at it). Samuel

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Samuel Thibault, le Fri 02 May 2014 11:57:53 +0200, a écrit : So we just need to fix guardsize in our libpthread. It was not so difficult actually. Svante, could you try this libpthread: http://people.debian.org/~sthibault/tmp/libpthread.so.0.3 Thanks, Samuel

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-02 Thread Samuel Thibault
Svante Signell, le Fri 02 May 2014 12:45:56 +0200, a écrit : On Fri, 2014-05-02 at 12:00 +0200, Samuel Thibault wrote: Samuel Thibault, le Fri 02 May 2014 11:57:53 +0200, a écrit : So we just need to fix guardsize in our libpthread. (And I'll have a look at it). Maybe this can fix

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-05-01 Thread Samuel Thibault
Hello, Svante Signell, le Thu 24 Apr 2014 10:39:10 +0200, a écrit : - Without split stack enabled around 70 libgo tests pass and 50 fails, most of them with a segfault. - Enabling split stack and using the libc Samuel built all 122 libgo tests fail with a segfault. Please provide segfault

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-18 Thread Samuel Thibault
Samuel Thibault, le Thu 17 Apr 2014 00:03:45 +0200, a écrit : Thomas Schwinge, le Wed 09 Apr 2014 09:36:42 +0200, a écrit : Well, the first step is to verify that TARGET_THREAD_SPLIT_STACK_OFFSET and similar configury is correct for the Hurd, I have added the corresponding field, so we can

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-16 Thread Samuel Thibault
Samuel Thibault, le Sat 12 Apr 2014 01:04:49 +0200, a écrit : Samuel Thibault, le Fri 11 Apr 2014 23:51:44 +0200, a écrit : So, do we really want to let munmap poke a hole at address 0 and thus let further vm_map() return address 0? i.e. we could apply this: I have applied it. Samuel

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-16 Thread Samuel Thibault
Thomas Schwinge, le Wed 09 Apr 2014 09:36:42 +0200, a écrit : Well, the first step is to verify that TARGET_THREAD_SPLIT_STACK_OFFSET and similar configury is correct for the Hurd, I have added the corresponding field, so we can just use the same offset as on Linux. Samuel

Re: Hurd port for gcc go PATCH 7-9 (9)

2014-04-14 Thread Samuel Thibault
Svante Signell, le Mon 14 Apr 2014 09:59:03 +0200, a écrit : @@ -528,6 +538,8 @@ # The stat type. # Prefer largefile variant if available. +# Special treatment of st_dev for GNU/Hurd +# /usr/include/i386-gnu/bits/stat.h: #define st_dev st_fsid stat=`grep '^type _stat64 '

Re: Hurd port for gcc go PATCH 0-3 (9)

2014-04-11 Thread Samuel Thibault
Svante Signell, le Fri 11 Apr 2014 14:47:21 +0200, a écrit : #ifdef TARGET_LIBC_PROVIDES_SSP +/* i386 glibc provides __stack_chk_guard in %gs:0x14. */ +#define TARGET_THREAD_SSP_OFFSET 0x14 Err, not the Hurd variant, no. Is it really needed? @@ -682,7 +686,7 @@ go_net_cgo_file =

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-11 Thread Samuel Thibault
Thomas Schwinge, le Wed 09 Apr 2014 09:36:42 +0200, a écrit : Well, the first step is to verify that TARGET_THREAD_SPLIT_STACK_OFFSET and similar configury is correct for the Hurd, It's not. I've checked what TARGET_THREAD_SPLIT_STACK_OFFSET is, it's an offset inside the tcbhead_t structure,

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-11 Thread Samuel Thibault
Samuel Thibault, le Fri 11 Apr 2014 23:51:44 +0200, a écrit : So, do we really want to let munmap poke a hole at address 0 and thus let further vm_map() return address 0? i.e. we could apply this: diff --git a/sysdeps/mach/munmap.c b/sysdeps/mach/munmap.c index 57d99f9..a46e3f1 100644

Re: GCC's -fsplit-stack disturbing Mach's vm_allocate

2014-04-04 Thread Samuel Thibault
Hello, Thomas Schwinge, le Wed 26 Jun 2013 23:30:03 +0200, a écrit : On Sat, 22 Jun 2013 08:15:46 -0700, Ian Lance Taylor i...@google.com wrote: Go can work without split stack. In that case libgo will use much larger stacks for goroutines, to reduce the chance of running out of stack

Re: GCC for GNU Hurd: MACH built-in preprocessor macro (was: gdb: FTBFS on hurd-i386 (for review))

2012-11-06 Thread Samuel Thibault
Thomas Schwinge, le Mon 05 Nov 2012 07:09:43 +0100, a écrit : Samuel, is there any way you can unpack all Debian source packages on a Debian machine, and run a recursive grep command (I can work out a suitable regex) to see where removing the MACH or __MACH built-in preprocessor macros might

Re: GCC for GNU Hurd: MACH built-in preprocessor macro (was: gdb: FTBFS on hurd-i386 (for review))

2012-11-05 Thread Samuel Thibault
Thomas Schwinge, le Mon 05 Nov 2012 07:09:43 +0100, a écrit : Samuel, is there any way you can unpack all Debian source packages on a Debian machine, and run a recursive grep command (I can work out a suitable regex) to see where removing the MACH or __MACH built-in preprocessor macros might