For the x86_64 ABI we want this to always fit into 1 byte. Even for
regular i686, msgt_name is always smaller than 25 (MACH_MSG_TYPE_LAST)
and we don't have plans to have more names.
Also throw an error if we deemed an RPC to be "TooLong" as that won't
work or work badly.
Tested by cross-compilin
Hello,
On Wed, May 10, 2023, 08:21 Flavio Cruz wrote:
> HAVE_MIG_RETCODE is removed completely since this will be a no-op either
> way (compiling against old Hurd headers will work the same, new Hurd
> headers will result in the same stubs since retcode is a no-op).
It is a no-op currently, but
We already did the same change for Hurd
(https://git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=ef5924402864ef049f40a39e73967628583bc1a4)
Due to MiG requiring the subsystem to be defined early in order to know the
size of a port, this was causing a division by zero error during ./configure.
We
Also fixed the implementation of default_pager_paging_storage_new in proxy
def pager to call into default_pager_paging_storage_new.
We can fast track the simplification of the RPC ABI for x86_64 if we don't have
MACH_MSG_TYPE_STRING used in RPCs which forces msgt_size to use more than 8
bits.
---
Jessica Clarke, le mer. 10 mai 2023 01:44:39 +0100, a ecrit:
> On 10 May 2023, at 01:26, Samuel Thibault wrote:
> >
> > Sergey Bugaev, le mar. 09 mai 2023 00:31:07 +0300, a ecrit:
> >> GCC was complaining about the mismatch in types between the 'fn' pointer
> >> and the function pointers assigned
Hello,
Pushed!
Sergey Bugaev, le mar. 09 mai 2023 00:30:55 +0300, a ecrit:
> One annoying warning that I get a lot of when building the Hurd with
> GCC 13 is -Wenum-int-mismatch; here's one example:
>
> ../../trans/streamio.c:694:1: warning: conflicting types for
> ‘trivfs_S_file_sync’ due to e
On 10 May 2023, at 01:26, Samuel Thibault wrote:
>
> Sergey Bugaev, le mar. 09 mai 2023 00:31:07 +0300, a ecrit:
>> GCC was complaining about the mismatch in types between the 'fn' pointer
>> and the function pointers assigned to it. Since fn is meant to be used
>> with different function types,
Sergey Bugaev, le mar. 09 mai 2023 00:31:07 +0300, a ecrit:
> GCC was complaining about the mismatch in types between the 'fn' pointer
> and the function pointers assigned to it. Since fn is meant to be used
> with different function types, represent it as a 'void *' and not a
> pointer to any part
I'm observing that build-many-glibcs.py runs can end up with modifications
to the source directory (which later cause problems with updating the
glibc checkout):
diff --git a/sysdeps/mach/hurd/bits/errno.h b/sysdeps/mach/hurd/bits/errno.h
index 069865189f..3b6363568d 100644
--- a/sysdeps/mach/hu
Flávio Cruz, le mar. 09 mai 2023 18:54:37 -0400, a ecrit:
> On Mon, May 8, 2023 at 4:40 PM Samuel Thibault <[1]samuel.thiba...@gnu.org>
> wrote:
>
> Hello,
>
> Flavio Cruz, le dim. 07 mai 2023 23:35:23 -0400, a ecrit:
> > We can fast track the simplification of the RPC ABI for x86_64
Flavio Cruz, le dim. 07 mai 2023 23:39:18 -0400, a ecrit:
> @@ -100,8 +100,9 @@ S_default_pager_paging_storage (mach_port_t pager,
>return 0;
> }
>
> +#ifndef __x86_64__
> kern_return_t
> -S_default_pager_paging_storage_new (mach_port_t pager,
> +S_default_pager_paging_storage (mach_port_t
Hello,
On Mon, May 8, 2023 at 4:40 PM Samuel Thibault
wrote:
> Hello,
>
> Flavio Cruz, le dim. 07 mai 2023 23:35:23 -0400, a ecrit:
> > We can fast track the simplification of the RPC ABI for x86_64 if we
> don't have
> > MACH_MSG_TYPE_STRING used in RPCs which forces msgt_size to use more
> tha
Add example of 64-bit debugging.
---
contributing.mdwn | 17 +
1 file changed, 17 insertions(+)
diff --git a/contributing.mdwn b/contributing.mdwn
index c4a3787d..90705d93 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -199,6 +199,23 @@ After you have a Hurd vm set up
13 matches
Mail list logo