Performance gain by avoiding arguments check is very small (less then 1%).

[Zack Weinberg]

On Mon, Sep 29, 2025, at 9:54 PM, Amit wrote:
> On Tue, Sep 30, 2025, 2:23 AM Wilco Dijkstra
> <Wilco.Dijkstra@arm.com> wrote:
>> Benchmarking is hard, much harder than you think. It is  done by
>> creating a tight loop around any code you want to measure. You have
>> to use inputs that are representative of real usage (ideally from
>> traces from actual workloads). For timing we use a high-resolution
>> (nano-second) timer. You can look at recent benchmarks in benchtests/
>> that show how it should be done.
>
> I am not going to get into any discussion because I have learned that
> glibc people are defensive people and they will defend their
> wrongdoings.

_You_ came to _us_ suggesting changes.  You don't have to make any
further arguments for your suggestions, if you don't want to, but if you
can't persuade us that what you suggest is a good idea, we're not going
to take your suggestions.

zw