public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein <goldstein.w.n@gmail.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Sunil Pandey <skpgkp2@gmail.com>, libc-alpha@sourceware.org
Subject: Re: [PATCH] x86_64: Exclude SSE, AVX and FMA4 variants in libm multiarch
Date: Tue, 20 Feb 2024 18:38:06 +0000	[thread overview]
Message-ID: <CAFUsyf+Ts6g=j3hAGREr_qJWhxVt0amAp0hko53PnG0XTRCuvw@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOoZcX1J9vnRy3XkNkJWnWOv9K0ygPT_3xVjT6df5NCnsA@mail.gmail.com>

On Tue, Feb 20, 2024 at 6:37 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>
> On Tue, Feb 20, 2024 at 10:32 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >
> > On Tue, Feb 20, 2024 at 6:28 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > >
> > > On Tue, Feb 20, 2024 at 10:19 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > >
> > > > On Tue, Feb 20, 2024 at 6:14 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > > > >
> > > > > On Tue, Feb 20, 2024 at 10:07 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > > > >
> > > > > > On Tue, Feb 20, 2024 at 6:05 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > > > > > >
> > > > > > > On Tue, Feb 20, 2024 at 9:56 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > > > > > >
> > > > > > > > On Tue, Feb 20, 2024 at 5:51 PM Sunil Pandey <skpgkp2@gmail.com> wrote:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Tue, Feb 20, 2024 at 9:34 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > > > > > > >>
> > > > > > > > >> On Tue, Feb 20, 2024 at 4:58 PM Sunil K Pandey <skpgkp2@gmail.com> wrote:
> > > > > > > > >> >
> > > > > > > > >> > When glibc is built with FMA and AVX2 enabled by default, the resulting
> > > > > > > > >> > glibc binaries won't run on SSE or FMA4 processors.  Exclude SSE, AVX and
> > > > > > > > >> > FMA4 variants in libm multiarch when both FMA and AVX2 are enabled by
> > > > > > > > >> > default.  Disallow glibc build with only AVX2 or FMA enabled as all AVX2
> > > > > > > > >> > processors, including VMs, should also support FMA and vice versa.
> > > > > > > > >> >
> > > > > > > > >> > When glibc is built with SSE4.1 enabled by default, only keep SSE4.1
> > > > > > > > >> > variant.
> > > > > > > > >> Not avx2 + FMA as well?
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > Correct. Logic is as follows
> > > > > > > > > If (build with AVX2+FMA): Keep AVX2+FMA variants only.
> > > > > > > > > else if (build with SSE4.1): Keep SSE4.1 variants only.
> > > > > > > > What if someone builds with sse4.1 as a minimum but then
> > > > > > > > runs on avx2+ machines?
> > > > > > >
> > > > > > > Only SSE4.1 variant will be used in this case.   Both SSE4.1
> > > > > > > and AVX versions only have a single instruction.  This matches
> > > > > > > the compiler builtin function of SS4.1 and AVX.
> > > > > >
> > > > > > if they are all the same, whats the rationale for having an
> > > > > > avx version at all?
> > > > >
> > > > > They aren't the same.  For ceil, it is
> > > > >
> > > > > roundsd $10, %xmm0, %xmm0
> > > > > ret
> > > > >
> > > > > vs
> > > > >
> > > > > vroundsd $10, %xmm0, %xmm0, %xmm0
> > > > > ret
> > > > >
> > > > > You get the same things with
> > > > >
> > > > > return __builtin_ceil (x);
> > > >
> > > > I mean if they are equal quality sse4.1 / avx,
> > > > why not just remove the avx impls are using sse4.1 impls
> > > > on avx targets?
> > >
> > > If glibc is compiled with AVX, we should use the AVX version if
> > > appropriate.   Since the minimum GCC for glibc build can't inline
> > >  __builtin_ceil, we inline  __builtin_ceil by hand.
> > if compiled with avx, but for generic target do we need to hold
> > onto avx versions for any reason?
>
> I don't understand what you were asking.   This patch leads to the same
> assembly code generated from
>
> double
> __ceil (double x)
> {
>   return __builtin_ceil (x);
> }
>
> by a GCC which can inline __builtin_ceil, compiling with -msse4.1 or -mavx.

Ahh, I had a misunderstanding, okay its clear sse4.1 makes sense.
>
> --
> H.J.

  reply	other threads:[~2024-02-20 18:38 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-20 16:58 Sunil K Pandey
2024-02-20 17:33 ` Noah Goldstein
2024-02-20 17:51   ` Sunil Pandey
2024-02-20 17:56     ` Noah Goldstein
2024-02-20 18:04       ` H.J. Lu
2024-02-20 18:07         ` Noah Goldstein
2024-02-20 18:13           ` H.J. Lu
2024-02-20 18:19             ` Noah Goldstein
2024-02-20 18:27               ` H.J. Lu
2024-02-20 18:32                 ` Noah Goldstein
2024-02-20 18:36                   ` H.J. Lu
2024-02-20 18:38                     ` Noah Goldstein [this message]
2024-02-20 18:48                     ` Adhemerval Zanella Netto
2024-02-20 18:54                       ` H.J. Lu
2024-02-20 19:02                         ` Adhemerval Zanella Netto
2024-02-20 19:10                           ` H.J. Lu
2024-02-20 19:56                             ` Adhemerval Zanella Netto
2024-02-20 20:03                               ` Adhemerval Zanella Netto
2024-02-20 20:18                                 ` Noah Goldstein
2024-02-20 20:27                                   ` H.J. Lu
2024-02-24  2:35                                     ` [PATCH v2] " Sunil K Pandey
2024-02-24 14:30                                       ` H.J. Lu
2024-02-24 14:55                                         ` H.J. Lu
2024-02-24 16:23                                       ` H.J. Lu
2024-02-24 16:27                                         ` H.J. Lu
2024-02-24 22:23                                           ` Sunil Pandey

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='CAFUsyf+Ts6g=j3hAGREr_qJWhxVt0amAp0hko53PnG0XTRCuvw@mail.gmail.com' \
    --to=goldstein.w.n@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=skpgkp2@gmail.com \
    /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).