> Would it be possible to limit use of the list to actually requesting
> help or making reports, rather than inciting debates about what is UB
> or what the consequences of UB might be?

You are right. 

The real question is: if we only need malloc_usable_size to return the size actually allocated internally (not the size requested by the user, **just as musl version 1.1 and all other libc implementations do**), is it possible to improve its time and space efficiency?

Thanks :-)

--

   Best Regards
  BaiYang
  baiyang@gmail.com
  http://i.baiy.cn
**** < END OF EMAIL > **** 
 
 
From: Rich Felker
Date: 2022-09-20 08:38
To: baiyang
CC: musl
Subject: Re: Re: [musl] The heap memory performance (malloc/free/realloc) is significantly degraded in musl 1.2 (compared to 1.1)
On Tue, Sep 20, 2022 at 08:25:52AM +0800, baiyang wrote:
> As Gabriel said, it's not a UB. Contrarily, it is a bug in gcc's Msan.
> Just read more on this thread :-) 
 
Would it be possible to limit use of the list to actually requesting
help or making reports, rather than inciting debates about what is UB
or what the consequences of UB might be?