public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Remove -fno-tree-loop-distribute-patterns usage on dl-support
Date: Tue, 9 Aug 2022 12:06:13 -0700	[thread overview]
Message-ID: <CAMe9rOqyLotgLN5HPqRZc=upvWVx+hTGBaPRFuFB1s4QAqxRTw@mail.gmail.com> (raw)
In-Reply-To: <9e01cc4b-7acd-5719-6615-8fb3cb6bf80b@linaro.org>

On Tue, Aug 9, 2022 at 11:48 AM Adhemerval Zanella Netto
<adhemerval.zanella@linaro.org> wrote:
>
>
>
> On 09/08/22 15:31, H.J. Lu wrote:
> > On Tue, Aug 9, 2022 at 5:11 AM Adhemerval Zanella Netto
> > <adhemerval.zanella@linaro.org> wrote:
> >>
> >>
> >>
> >> On 08/08/22 19:16, H.J. Lu wrote:
> >>
> >>>> --- a/sysdeps/x86_64/multiarch/memset-evex-unaligned-erms.S
> >>>> +++ b/sysdeps/x86_64/multiarch/memset-evex-unaligned-erms.S
> >>>> @@ -44,4 +44,7 @@
> >>>>
> >>>>  # define USE_LESS_VEC_MASK_STORE       1
> >>>>  # include "memset-vec-unaligned-erms.S"
> >>>> +# if !defined NO_MULTIARCH && MINIMUM_X86_ISA_LEVEL >= 4
> >>>> +strong_alias (__memset_evex_unaligned, __memset_generic)
> >>>> +# endif
> >>>>  #endif
> >>>
> >>> This will define 2 __memset_generic for -march=x86-64-v4.
> >>
> >> Are you sure? Check with a x86_64 build with -march=x86-64-v4 I am seeing:
> >>
> >> $ readelf -Ws string/memset*.os | grep -w __memset_generic | wc -l
> >> 1
> >>
> >> And it is indeed provided only by string/memset-evex-unaligned-erms.os.
> >
> > You are right.  Since dl-symbol-hacks.h defines memset to an alias,
> > should it be moved to sysdes/generic and each arch can provide a
> > suitable alias?
>
> The dl-symbol-hacks.h is meant to be used solely by loader code (that's
> why I have added to elf/), but I don't have a strong preference.

The default should be no alias.  Only IFUNC targets need to define a
proper alias.

-- 
H.J.

  reply	other threads:[~2022-08-09 19:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-08 20:00 Adhemerval Zanella
2022-08-08 22:16 ` H.J. Lu
2022-08-09 12:11   ` Adhemerval Zanella Netto
2022-08-09 18:31     ` H.J. Lu
2022-08-09 18:48       ` Adhemerval Zanella Netto
2022-08-09 19:06         ` H.J. Lu [this message]
2022-08-09 19:32           ` Adhemerval Zanella Netto
2022-08-09 19:34             ` H.J. Lu
2022-08-09 19:40               ` Adhemerval Zanella Netto
2022-08-09 21:51                 ` H.J. Lu
2022-08-10 13:12                   ` Adhemerval Zanella Netto
2022-08-10  3:37 ` Noah Goldstein
2022-08-10 13:04   ` Adhemerval Zanella Netto

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='CAMe9rOqyLotgLN5HPqRZc=upvWVx+hTGBaPRFuFB1s4QAqxRTw@mail.gmail.com' \
    --to=hjl.tools@gmail.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).