unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Noah Goldstein via Libc-alpha <libc-alpha@sourceware.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH 5/5] x86_64: Add evex optimized bcmp implementation in bcmp-evex.S
Date: Mon, 13 Sep 2021 22:40:18 -0500	[thread overview]
Message-ID: <CAFUsyfLM_M63uykH0-mB=yy+5=JjM0SHKg-Cj2qDE7g_JNJMdQ@mail.gmail.com> (raw)
In-Reply-To: <e2fd7a17-7f06-f69d-5b73-e1e7b59a8f99@redhat.com>

On Mon, Sep 13, 2021 at 9:35 PM Carlos O'Donell <carlos@redhat.com> wrote:

> On 9/13/21 10:05 PM, Noah Goldstein wrote:
> > On Mon, Sep 13, 2021 at 8:18 PM Carlos O'Donell <carlos@redhat.com>
> wrote:
> >
> >> On 9/13/21 7:05 PM, Noah Goldstein via Libc-alpha wrote:
> >>> No bug. This commit adds new optimized bcmp implementation for evex.
> >>>
> >>> The primary optimizations are 1) skipping the logic to find the
> >>> difference of the first mismatched byte and 2) not updating src/dst
> >>> addresses as the non-equals logic does not need to be reused by
> >>> different areas.
> >>>
> >>> The entry alignment has been fixed at 64. In throughput sensitive
> >>> functions which bcmp can potentially be frontend loop performance is
> >>> important to opimized for. This is impossible/difficult to do/maintain
> >>> with only 16 byte fixed alignment.
> >>>
> >>> test-memcmp, test-bcmp, and test-wmemcmp are all passing.
> >>
> >> This series fails in the containerized 32-bit x86 CI/CD regression
> tester.
> >>
> >>
> https://patchwork.sourceware.org/project/glibc/patch/20210913230506.546749-5-goldstein.w.n@gmail.com/
> >
> >
> > Shoot.
>
> No worries! That's what the CI/CD system is there for :-)
>
> > AFAICT the first error is:
> > *** No rule to make target '/build/string/stamp.os', needed by
> > '/build/libc_pic.a'.
>
> I think a normal 32-bit x86 builds should show this issue.
>
> You need a gcc that accepts -m32.
>

Was able to get it with DJ's command.

>
> I minimally set:
> export CC="gcc -m32 -Wl,--build-id=none"
> export CXX="g++ -m32 -Wl,--build-id=none"
> export CFLAGS="-g -O2 -march=i686 -Wl,--build-id=none"
> export CXXFLAGS="-g -O2 -march=i686 -Wl,--build-id=none"
> export CPPFLAGS="-g -O2 -march=i686 -Wl,--build-id=none"
>
> Then build with --host.
>
> e.g.
>
> /home/carlos/src/glibc-work/configure --host i686-pc-linux-gnu CC=gcc -m32
> -Wl,--build-id=none CFLAGS=-g -O2 -march=i686 -Wl,--build-id=none
> CPPFLAGS=-g -O2 -march=i686 -Wl,--build-id=none CXX=g++ -m32
> -Wl,--build-id=none CXXFLAGS=-g -O2 -march=i686 -Wl,--build-id=none
> --prefix=/usr
> --with-headers=/home/carlos/build/glibc-headers-work-i686/include
> --with-selinux --disable-nss-crypt --enable-bind-now --enable-static-pie
> --enable-systemtap --enable-hardcoded-path-in-tests --enable-tunables=yes
> --enable-add-ons


Thanks for the help!


>


> > Also, does anyone know what make/configure commands I need to reproduce
> > this on a x86_64-Linux machine? The build log doesn't appear to have the
> command.
>
> DJ, Should the trybot log the configure step?
>
>
So I think I was able to fix the build by making a new file in
glibc/string/bcmp.c
and just having bcmp call memcmp

Is there another/better way to fix the build?  I don't think it's really
fair that every
arch other than x86_64 should have to pay an extra function call cost to
use bcmp.


> --
> Cheers,
> Carlos.
>
>

  parent reply	other threads:[~2021-09-14  3:40 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-13 23:05 [PATCH 1/5] x86_64: Add support for bcmp using sse2, sse4_1, avx2, and evex Noah Goldstein via Libc-alpha
2021-09-13 23:05 ` [PATCH 2/5] x86_64: Add sse2 optimized bcmp implementation in memcmp.S Noah Goldstein via Libc-alpha
2021-09-13 23:05 ` [PATCH 3/5] x86_64: Add sse4_1 optimized bcmp implementation in memcmp-sse4.S Noah Goldstein via Libc-alpha
2021-09-13 23:05 ` [PATCH 4/5] x86_64: Add avx2 optimized bcmp implementation in bcmp-avx2.S Noah Goldstein via Libc-alpha
2021-09-13 23:05 ` [PATCH 5/5] x86_64: Add evex optimized bcmp implementation in bcmp-evex.S Noah Goldstein via Libc-alpha
2021-09-14  1:18   ` Carlos O'Donell via Libc-alpha
2021-09-14  2:05     ` Noah Goldstein via Libc-alpha
2021-09-14  2:35       ` Carlos O'Donell via Libc-alpha
2021-09-14  2:55         ` DJ Delorie via Libc-alpha
2021-09-14  3:24           ` Noah Goldstein via Libc-alpha
2021-09-14  3:40         ` Noah Goldstein via Libc-alpha [this message]
2021-09-14  4:21           ` DJ Delorie via Libc-alpha
2021-09-14  5:29             ` Noah Goldstein via Libc-alpha
2021-09-14  5:42               ` DJ Delorie via Libc-alpha
2021-09-14  5:55                 ` Noah Goldstein via Libc-alpha
2021-09-13 23:22 ` [PATCH 1/5] x86_64: Add support for bcmp using sse2, sse4_1, avx2, and evex Noah Goldstein via Libc-alpha
2021-09-14  6:30 ` [PATCH v2 " Noah Goldstein via Libc-alpha
2021-09-14  6:30   ` [PATCH v2 2/5] x86_64: Add sse2 optimized bcmp implementation in memcmp.S Noah Goldstein via Libc-alpha
2021-09-14  6:30   ` [PATCH v2 3/5] x86_64: Add sse4_1 optimized bcmp implementation in memcmp-sse4.S Noah Goldstein via Libc-alpha
2021-09-14  6:30   ` [PATCH v2 4/5] x86_64: Add avx2 optimized bcmp implementation in bcmp-avx2.S Noah Goldstein via Libc-alpha
2021-09-14  6:30   ` [PATCH v2 5/5] x86_64: Add evex optimized bcmp implementation in bcmp-evex.S Noah Goldstein via Libc-alpha
2021-09-14 14:40   ` [PATCH v2 1/5] x86_64: Add support for bcmp using sse2, sse4_1, avx2, and evex H.J. Lu via Libc-alpha
2021-09-14 19:23     ` Noah Goldstein via Libc-alpha
2021-09-14 20:30     ` Florian Weimer via Libc-alpha
2021-09-15  0:00 ` [PATCH " Joseph Myers
2021-09-15 13:37   ` Zack Weinberg via Libc-alpha
2021-09-15 14:01     ` Re: [PATCH 1/5] x86_64: Add support for bcmp using sse2, sse 4_1, " Florian Weimer via Libc-alpha
2021-09-15 18:06       ` Noah Goldstein via Libc-alpha
2021-09-15 18:30         ` Joseph Myers
2021-09-27  1:35           ` Noah Goldstein via Libc-alpha
2021-09-27  7:29             ` Florian Weimer via Libc-alpha
2021-09-27 16:49               ` Noah Goldstein via Libc-alpha
2021-09-27 16:54                 ` Florian Weimer via Libc-alpha
2021-09-27 17:54                   ` Noah Goldstein via Libc-alpha
2021-09-27 17:56                     ` Florian Weimer via Libc-alpha
2021-09-27 18:05                       ` Noah Goldstein via Libc-alpha
2021-09-27 18:10                         ` Florian Weimer via Libc-alpha
2021-09-27 18:15                           ` Noah Goldstein via Libc-alpha
2021-09-27 18:22                             ` Florian Weimer via Libc-alpha
2021-09-27 18:34                               ` Noah Goldstein via Libc-alpha
2021-09-27 18:56                                 ` Florian Weimer via Libc-alpha
2021-09-27 19:20                                   ` Noah Goldstein via Libc-alpha
2021-09-27 19:34                                     ` Florian Weimer via Libc-alpha
2021-09-27 19:43                                       ` Noah Goldstein via Libc-alpha
2021-09-27 19:59                                         ` Florian Weimer via Libc-alpha
2021-09-27 20:22                                           ` Noah Goldstein via Libc-alpha
2021-09-27 20:24                                             ` Florian Weimer via Libc-alpha
2021-09-27 20:38                                               ` Noah Goldstein via Libc-alpha
2021-09-28  0:07                                                 ` Noah Goldstein via Libc-alpha
2021-09-27 17:42               ` Joseph Myers
2021-09-27 17:48                 ` Noah Goldstein via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFUsyfLM_M63uykH0-mB=yy+5=JjM0SHKg-Cj2qDE7g_JNJMdQ@mail.gmail.com' \
    --to=libc-alpha@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=goldstein.w.n@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).