From: Joseph Myers <joseph@codesourcery.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v4 3/5] x86: Optimize strcmp-avx2.S
Date: Fri, 4 Feb 2022 18:57:03 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202041856290.244210@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20220203214215.3275256-3-goldstein.w.n@gmail.com>
I've seeing a build failure for x32 that looks likely to be caused by this
patch.
../sysdeps/x86_64/multiarch/strcmp-avx2.S: Assembler messages:
../sysdeps/x86_64/multiarch/strcmp-avx2.S:109: Error: unsupported instruction `mov'
/scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-x32/glibc/sysd-rules:847: recipe for target '/scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-x32/glibc/string/strncmp-avx2.o' failed
make[3]: *** [/scratch/jmyers/glibc-bot/build/glibcs/x86_64-linux-gnu-x32/glibc/string/strncmp-avx2.o] Error 1
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-04 18:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 21:42 [PATCH v4 1/5] string/test-str*cmp: remove stupid_[strcmp, strncmp, wcscmp, wcsncmp] Noah Goldstein
2022-02-03 21:42 ` [PATCH v4 2/5] string: Improve coverage in test-strcmp.c and test-strncmp.c Noah Goldstein
2022-02-03 22:28 ` H.J. Lu
2022-02-07 13:59 ` Matheus Castanho
2022-02-07 19:03 ` Noah Goldstein
2022-02-07 20:17 ` Noah Goldstein
2022-02-03 21:42 ` [PATCH v4 3/5] x86: Optimize strcmp-avx2.S Noah Goldstein
2022-02-03 22:29 ` H.J. Lu
2022-02-04 18:57 ` Joseph Myers [this message]
2022-02-04 19:13 ` H.J. Lu
2022-05-04 5:40 ` Sunil Pandey
2022-02-03 21:42 ` [PATCH v4 4/5] x86: Optimize strcmp-evex.S Noah Goldstein
2022-02-03 22:30 ` H.J. Lu
2022-05-04 5:38 ` Sunil Pandey
2022-02-03 21:42 ` [PATCH v4 5/5] benchtests: Add more coverage for strcmp and strncmp benchmarks Noah Goldstein
2022-02-03 22:30 ` H.J. Lu
2022-02-03 22:28 ` [PATCH v4 1/5] string/test-str*cmp: remove stupid_[strcmp, strncmp, wcscmp, wcsncmp] H.J. Lu
2022-02-03 23:30 ` Noah Goldstein
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=alpine.DEB.2.22.394.2202041856290.244210@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=goldstein.w.n@gmail.com \
--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).