From: Joseph Myers <joseph@codesourcery.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v1 1/6] String: Add __memcmpeq as build target
Date: Thu, 28 Oct 2021 17:57:00 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2110281754490.1736839@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20211027024323.1199441-1-goldstein.w.n@gmail.com>
One of the patches in this series has broken the testsuite build for
x86_64 --disable-multi-arch.
string/tester.o: in function `test_memcmpeq':
/scratch/jmyers/glibc-bot/src/glibc/string/tester.c:1456: undefined reference to `__memcmpeq'
https://sourceware.org/pipermail/libc-testresults/2021q4/008775.html
(11c88336e3013653d473fd58d8658d0cd30887e3 was OK,
9b7cfab1802b71763da00982f772208544cf4a95 fails, so it's definitely
something in this series.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-10-28 17:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 2:43 Noah Goldstein
2021-10-27 2:43 ` [PATCH v1 2/6] Benchtests: Add benchtests for __memcmpeq Noah Goldstein
2021-10-27 12:45 ` H.J. Lu
2021-10-27 16:08 ` Noah Goldstein
2021-10-27 16:07 ` [PATCH v2 " Noah Goldstein
2021-10-27 17:59 ` H.J. Lu
2021-10-27 2:43 ` [PATCH v1 3/6] x86_64: Add support for __memcmpeq using sse2, avx2, and evex Noah Goldstein
2021-10-27 12:47 ` H.J. Lu
2021-10-27 2:43 ` [PATCH v1 4/6] x86_64: Add sse2 optimized __memcmpeq in memcmp-sse2.S Noah Goldstein
2021-10-27 12:48 ` H.J. Lu
2021-10-27 2:43 ` [PATCH v1 5/6] x86_64: Add avx2 optimized __memcmpeq in memcmpeq-avx2.S Noah Goldstein
2021-10-27 12:48 ` H.J. Lu
2021-10-27 2:43 ` [PATCH v1 6/6] x86_64: Add evex optimized __memcmpeq in memcmpeq-evex.S Noah Goldstein
2021-10-27 2:44 ` Noah Goldstein
2021-10-27 12:49 ` H.J. Lu
2021-10-27 12:42 ` [PATCH v1 1/6] String: Add __memcmpeq as build target H.J. Lu
2021-10-27 18:46 ` Noah Goldstein
2021-10-28 17:57 ` Joseph Myers [this message]
2021-10-28 18:25 ` 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.2110281754490.1736839@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).