From: Samuel Thibault <samuel.thibault@gnu.org>
To: Guy-Fleury Iteriteka <gfleury@disroot.org>
Cc: libc-alpha@sourceware.org, bug-hurd@gnu.org
Subject: Re: [PATCH 0/3] htl: move __pthtread_total, ___pthread_self, pthread_self
Date: Tue, 3 Jan 2023 22:50:05 +0100 [thread overview]
Message-ID: <20230103215005.eqb3onajx6oyegu7@begin> (raw)
In-Reply-To: <20230103104515.324527-1-gfleury@disroot.org>
Hello,
Apart from the symbols visibility, that looks good to me, thanks!
We're however in glibc slushy ABI freeze period, I guess we should
refrain from including this patch for 2.37?
The release is expected on february 1st, in the meanwhile you can work
on moving the other symbols. Ideally we'll have moved all the symbols by
2.38 :)
Samuel
Guy-Fleury Iteriteka via Libc-alpha, le mar. 03 janv. 2023 12:45:12 +0200, a ecrit:
> With this patch i boot up a hurd system with flavio scripts.
>
> Guy-Fleury Iteriteka (3):
> htl: move __pthtread_total into libc
> htl: move __pthread_self into libc.
> htl: move pthread_self into libc
>
> htl/Makefile | 3 +--
> htl/Versions | 15 ++++++++++++---
> htl/forward.c | 4 ----
> htl/pt-create.c | 6 ------
> htl/pt-initialize.c | 1 -
> htl/pt-internal.h | 2 ++
> htl/pt-nthreads.c | 23 +++++++++++++++++++++++
> htl/pt-self.c | 8 ++++++--
> sysdeps/htl/pthread-functions.h | 2 --
> sysdeps/mach/hurd/htl/pt-pthread_self.c | 22 ++++++++++++++++++++++
> sysdeps/mach/hurd/htl/pt-sysdep.c | 2 --
> sysdeps/mach/hurd/htl/pt-sysdep.h | 3 +++
> sysdeps/mach/hurd/i386/libc.abilist | 2 ++
> sysdeps/mach/hurd/i386/libpthread.abilist | 2 --
> 14 files changed, 71 insertions(+), 24 deletions(-)
> create mode 100644 htl/pt-nthreads.c
> create mode 100644 sysdeps/mach/hurd/htl/pt-pthread_self.c
>
> --
> 2.38.1
next prev parent reply other threads:[~2023-01-03 21:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 10:45 Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 1/3] htl: move __pthtread_total into libc Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 2/3] htl: move ___pthread_self " Guy-Fleury Iteriteka
2023-01-03 10:45 ` [PATCH 3/3] htl: move pthread_self " Guy-Fleury Iteriteka
2023-01-03 21:50 ` Samuel Thibault
2023-01-03 23:02 ` Samuel Thibault
2023-01-03 17:22 ` [PATCH 0/3] htl: move __pthtread_total, ___pthread_self, pthread_self Zack Weinberg
2023-01-03 18:28 ` Samuel Thibault
2023-01-09 21:59 ` Zack Weinberg
2023-01-03 18:30 ` Guy-Fleury Iteriteka
2023-01-03 21:50 ` Samuel Thibault [this message]
2023-01-04 8:49 ` gfleury
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230103215005.eqb3onajx6oyegu7@begin \
--to=samuel.thibault@gnu.org \
--cc=bug-hurd@gnu.org \
--cc=gfleury@disroot.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).