public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v2] Move libc_freeres_ptrs and libc_subfreeres to hidden/weak functions
Date: Tue, 13 Dec 2022 12:46:26 -0300	[thread overview]
Message-ID: <ec381bec-cf61-fcfb-fbad-3f5ba3ec5057@linaro.org> (raw)
In-Reply-To: <87lenba0az.fsf@oldenburg.str.redhat.com>



On 13/12/22 10:41, Florian Weimer wrote:
> * Adhemerval Zanella:
> 
>> -#define __libc_freeres_fn_section \
>> -  __attribute__ ((__used__, section ("__libc_freeres_fn")))
> 
> I think we could keep __libc_freeres_fn_section for documentation and
> optimization purposes.  A section name such as ".text.__libc_freeres_fn"
> won't need generic linker script support.
> 
>> +#ifdef SHARED
>> +#define set_freeres_declare_ptr(__name, __ptr)			\
>> +  void __name (void)						\
>> +  {								\
>> +    free (__ptr);						\
>> +  }
>> +#else
>> +#define set_freeres_declare_name(__name)			\
>> +  __name ## _aux
>> +#define set_freeres_declare_ptr(__name, __ptr)			\
>> +  void set_freeres_declare_name (__name) (void)			\
>> +  {								\
>> +    if (__ptr != NULL)						\
>> +      free (__ptr);						\
>> +  }								\
>> +  weak_alias (set_freeres_declare_name (__name),  __name)
>> +#endif
> 
> What's the benefit of going through the function, instead of freeing the
> variable directly?
> 
>   if (&ptr != NULL)
>     free (ptr);
> 
> should work for a weak variable, too.

Right, I did not get your suggestion before. I will adjust it.

      reply	other threads:[~2022-12-13 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 12:20 Adhemerval Zanella
2022-12-13 12:30 ` Andreas Schwab
2022-12-13 15:45   ` Adhemerval Zanella Netto
2022-12-13 13:41 ` Florian Weimer
2022-12-13 15:46   ` Adhemerval Zanella Netto [this message]

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=ec381bec-cf61-fcfb-fbad-3f5ba3ec5057@linaro.org \
    --to=adhemerval.zanella@linaro.org \
    --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).