public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Szabolcs Nagy <Szabolcs.Nagy@arm.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
	 Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>,
	 'GNU C Library' <libc-alpha@sourceware.org>
Subject: Re: [PATCH] AArch64: Add support for MOPS memcpy/memmove/memset
Date: Sun, 22 Oct 2023 00:12:49 +0200	[thread overview]
Message-ID: <87h6mjk4ke.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <ZTKlF4gJD/E6rTgr@arm.com> (Szabolcs Nagy's message of "Fri, 20 Oct 2023 17:04:39 +0100")

* Szabolcs Nagy:

> i think the __GI_foo alias to foo is only needed if foo is an
> exported sym, then it can avoid a PLT when foo called internally.
>
> i think we should just drop these macros in the multiarch asm.
> (and fix things up e.g. if asm code is directly included across
> multiarch and generic code such that only generic exported syms
> get the alias)

We might want to start exporting the alternative implementation under
GLIBC_PRIVATE names, so that we can find them in the dynamic symbol
table.  Then we could have an LD_DEBUG mode that prints these function
symbols, translated from the function addresses returned from IFUNC
resolvers.  I think this would be a really useful diagnostic tool.

Thanks,
Florian


  reply	other threads:[~2023-10-21 22:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 15:37 Wilco Dijkstra
2023-10-19 17:03 ` Adhemerval Zanella Netto
2023-10-20 15:19   ` Wilco Dijkstra
2023-10-20 15:56     ` Adhemerval Zanella Netto
2023-10-20 16:04     ` Szabolcs Nagy
2023-10-21 22:12       ` Florian Weimer [this message]
2023-10-23 12:35       ` 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=87h6mjk4ke.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=Szabolcs.Nagy@arm.com \
    --cc=Wilco.Dijkstra@arm.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).