public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb-ng.enyo.de>
To: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Replace memcmp with __memcmpeq for variable size
Date: Sun, 06 Feb 2022 23:19:14 +0100	[thread overview]
Message-ID: <874k5b3afx.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20220206210914.1593336-1-hjl.tools@gmail.com> (H. J. Lu via Libc-alpha's message of "Sun, 6 Feb 2022 13:09:14 -0800")

* H. J. Lu via Libc-alpha:

> diff --git a/elf/dl-cache.c b/elf/dl-cache.c
> index 88bf78ad7c..8574d4ded1 100644
> --- a/elf/dl-cache.c
> +++ b/elf/dl-cache.c
> @@ -72,7 +72,7 @@ glibc_hwcaps_compare (uint32_t left_index, struct dl_hwcaps_priority *right)
>      to_compare = left_name_length;
>    else
>      to_compare = right->name_length;
> -  int cmp = memcmp (left_name, right->name, to_compare);
> +  int cmp = memcmp_eq (left_name, right->name, to_compare);
>    if (cmp != 0)
>      return cmp;
>    if (left_name_length < right->name_length)

This change is not correct.

The x86-specific <memcmp-eq.h> optimization probably applies to other
targets as well.  I also do not quite see where the performance
benefits come from.  None of the changed spots look particularly hot
to me.

And I thought the assumption was that GCC would perform this optimization?

  reply	other threads:[~2022-02-06 22:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-06 21:09 H.J. Lu
2022-02-06 22:19 ` Florian Weimer [this message]
2022-02-07  0:20   ` H.J. Lu
2022-02-07 10:40     ` Florian Weimer
2022-02-07 13:13       ` H.J. Lu
2022-02-07 13:19         ` Florian Weimer
2022-02-07 13:27           ` H.J. Lu
2022-02-07 13:30             ` Adhemerval Zanella
2022-02-07 14:00               ` H.J. Lu
2022-02-07 20:35 ` Joseph Myers
2022-02-08 22:30 Wilco Dijkstra
2022-02-08 23:00 ` Adhemerval Zanella
2022-02-09  0:07   ` Noah Goldstein
2022-02-09  1:42     ` Wilco Dijkstra

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=874k5b3afx.fsf@mid.deneb.enyo.de \
    --to=fw@deneb-ng.enyo.de \
    --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).