From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Introduce to _dl_call_fini
Date: Fri, 21 Oct 2022 20:24:12 +0200 [thread overview]
Message-ID: <878rl9827n.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <865a135b-fb4a-2fa2-b858-105fa0e148ac@linaro.org> (Adhemerval Zanella Netto's message of "Fri, 21 Oct 2022 14:51:20 -0300")
* Adhemerval Zanella Netto:
> On 13/10/22 08:35, Florian Weimer via Libc-alpha wrote:
>> This consolidates the destructor invocations from _dl_fini and
>> dlclose. Remove the micro-optimization that avoids
>> calling _dl_call_fini if they are no destructors (as dlclose is quite
>> expensive anyway).
>>
>
> LGTM, I think the debug message change should be ok. Some comment on
> the old code you refactored.
Should I fix this and repost? Reviewed-by: plus suggestions is kind of
confusing. 8-)
Thanks,
Florian
next prev parent reply other threads:[~2022-10-21 18:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 11:35 Florian Weimer
2022-10-13 12:03 ` Andreas Schwab
2022-10-13 12:11 ` Florian Weimer
2022-10-21 17:51 ` Adhemerval Zanella Netto
2022-10-21 18:24 ` Florian Weimer [this message]
2022-10-21 18:40 ` Adhemerval Zanella Netto
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=878rl9827n.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=adhemerval.zanella@linaro.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).