On Fri, Feb 17, 2023 at 9:02 AM Flávio Cruz wrote:
> Thanks for the instructions. I discovered that mach_msg_type_long_t does not
> align to 8 bytes so it also needs a bit of padding just like mach_msg_type_t.
> See my last patch. I was able to compile most of the glibc and all the stubs
> afte
Applied, thanks!
Flavio Cruz via Libc-alpha, le ven. 17 févr. 2023 01:16:09 -0500, a ecrit:
> We already use the mach/machine include pattern in some other places so
> seems fine to make it consistent here too.
> ---
> sysdeps/mach/hurd/i386/htl/pt-machdep.c | 4 ++--
> sysdeps/mach/hurd/i386/tls
> With this layout alignment issues seem much simpler to solve, basically
> we can leave the compiler find the best combination for the second part
> of the message, and if the user/kernel archs are the same, the struct
> will have the same layout in the sending and receiving mig stubs.
To be clea
Follow-up Comment #36, sr #110199 (project administration):
First, it isn't clear to me from your comment if you checked all files in your
tarball. When I say 'all' I mean a procedure like find . -type f -print0 |
xargs -o0 $EDITOR and so on, and I implied that you would run it. You should
be ab
