From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org, Carlos O'Donell <carlos@redhat.com>
Subject: Re: libpthread removal in 2.34
Date: Fri, 12 Mar 2021 10:11:32 -0300 [thread overview]
Message-ID: <57bb461a-44d6-b951-8492-6f0c34d4f706@linaro.org> (raw)
In-Reply-To: <87ft119xiu.fsf@oldenburg.str.redhat.com>
On 11/03/2021 18:43, Florian Weimer wrote:
> * Adhemerval Zanella:
>
>> I can help you on the libpthread removal project, if you want help on work
>> besides review you can lay out the missing interfaces and work work in
>> parallel.
>
> I think we should probably swap between reviews and writing patches.
> Splitting up the work seems hard because of the Makefile and Versions
> conflicts that are difficult to avoid. I have an abilist merger, which
> should at least help with incorporating symbol additions due to
> unrelated glibc work.
I consider the merge issue a minor issue, since it is just a mechanical
step to actually fix it.
>
> I have a bunch of pending patches in Patchwork right now. The next step
> after that will be moving the cancellation implementation, then
> mutex/condvar (probably in one big patch). I had started on the
> mutex/condvar step before, but ran into unwinding interactions (hence
> the present series) and the private-futex issue. All this should cut
> down struct pthread_functions by quite a bit.
>
> Removing the $(pthread-compat-wrappers) seems largely independent of
> that. These symbols sort separately in the Versions file, too. If you
> could work on that, it would definitely help. I suggest to follow the
> one-commit-per-file approach, in case we need to track down regressions.
> (My present series already removes longjmp.)
Alright, I will focus on $(pthread-compat-wrappers), I have been working
on some already and I will finish it then.
next prev parent reply other threads:[~2021-03-12 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 11:26 Florian Weimer
2021-03-11 14:26 ` Carlos O'Donell
2021-03-11 17:32 ` Adhemerval Zanella
2021-03-11 21:43 ` Florian Weimer
2021-03-12 13:11 ` Adhemerval Zanella [this message]
2021-03-11 19:21 ` Florian Weimer
2021-03-11 22:45 ` Carlos O'Donell
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=57bb461a-44d6-b951-8492-6f0c34d4f706@linaro.org \
--to=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--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).