From: Guy-Fleury Iteriteka <gfleury@disroot.org>
To: libc-alpha@sourceware.org
Cc: Guy-Fleury Iteriteka <gfleury@disroot.org>
Subject: [PATCH 0/3] htl: move some symbol into libc
Date: Sat, 18 Mar 2023 11:58:23 +0200 [thread overview]
Message-ID: <20230318095826.1125734-1-gfleury@disroot.org> (raw)
Hello,
this attempt to move pthread_self first and will try others as i get
experiencces.
I boostrap a hurd with this scripts https://github.com/flavioc/cross-hurd
Guy-Fleury Iteriteka (3):
htl: move __pthtread_total into libc
htl: move ___pthread_self into libc.
htl: move pthread_self info 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 | 1 +
htl/pt-nthreads.c | 23 +++++++++++++++++++++++
htl/pt-self.c | 13 +++++++++++--
sysdeps/htl/pthread-functions.h | 2 --
sysdeps/htl/pthreadP.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 | 3 +++
sysdeps/mach/hurd/i386/libpthread.abilist | 2 --
15 files changed, 78 insertions(+), 24 deletions(-)
create mode 100644 htl/pt-nthreads.c
create mode 100644 sysdeps/mach/hurd/htl/pt-pthread_self.c
--
2.30.2
next reply other threads:[~2023-03-18 9:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-18 9:58 Guy-Fleury Iteriteka [this message]
2023-03-18 9:58 ` [PATCH 1/3] htl: move __pthtread_total " Guy-Fleury Iteriteka
2023-04-04 23:27 ` Samuel Thibault
2023-03-18 9:58 ` [PATCH 2/3] htl: move ___pthread_self " Guy-Fleury Iteriteka
2023-04-04 23:27 ` Samuel Thibault
2023-03-18 9:58 ` [PATCH 3/3] htl: move pthread_self info libc Guy-Fleury Iteriteka
2023-04-04 23:35 ` Samuel Thibault
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=20230318095826.1125734-1-gfleury@disroot.org \
--to=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).