From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] x86-64: Update tst-glibc-hwcaps-2.c for x86-64 baseline
Date: Fri, 22 Jan 2021 13:56:04 -0300 [thread overview]
Message-ID: <deb8ca59-61e6-d0e3-90b2-fb21a31bffae@linaro.org> (raw)
In-Reply-To: <CAMe9rOqaJ3M9g-4bBswp362pGEiSvQ+ggZGdnxg_rO3fsAKCnA@mail.gmail.com>
On 22/01/2021 12:01, H.J. Lu via Libc-alpha wrote:
> On Thu, Jan 21, 2021 at 4:49 PM H.J. Lu <hjl.tools@gmail.com> wrote:
>>
>> Return EXIT_FAILURE only if the level 2 libx86-64-isa-level.so is used
>> on x86-64 baseline machine.
>> ---
>> sysdeps/unix/sysv/linux/x86_64/tst-glibc-hwcaps-2.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/sysdeps/unix/sysv/linux/x86_64/tst-glibc-hwcaps-2.c b/sysdeps/unix/sysv/linux/x86_64/tst-glibc-hwcaps-2.c
>> index 2d8f7ec462..b223420089 100644
>> --- a/sysdeps/unix/sysv/linux/x86_64/tst-glibc-hwcaps-2.c
>> +++ b/sysdeps/unix/sysv/linux/x86_64/tst-glibc-hwcaps-2.c
>> @@ -51,7 +51,7 @@ do_test (void)
>> case 2:
>> /* The default libx86-64-isa-level.so is used. */
>> printf ("The default shared library is used.\n");
>> - if (has_isa_v3 || has_isa_v4 || !has_isa_v2)
>> + if (has_isa_v3 || has_isa_v4 || (!has_isa_v2 && level == 2))
>> ret = EXIT_FAILURE;
>> else
>> ret = EXIT_SUCCESS;
>> --
>> 2.29.2
Ok for 2.33.
prev parent reply other threads:[~2021-01-22 16:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 0:49 [PATCH] x86-64: Update tst-glibc-hwcaps-2.c for x86-64 baseline H.J. Lu via Libc-alpha
2021-01-22 15:01 ` H.J. Lu via Libc-alpha
2021-01-22 16:56 ` Adhemerval Zanella via Libc-alpha [this message]
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=deb8ca59-61e6-d0e3-90b2-fb21a31bffae@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.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).