public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Sunil K Pandey <skpgkp2@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86_64: Disable libmvec tests if multiarch not enabled [BZ# 28869]
Date: Wed, 23 Feb 2022 14:54:14 -0800	[thread overview]
Message-ID: <CAMe9rOqiUyx3vDCFcfLWTN-Tx=YgqvJJsS1fQ3hG910cj16hwA@mail.gmail.com> (raw)
In-Reply-To: <20220223224255.2077646-1-skpgkp2@gmail.com>

On Wed, Feb 23, 2022 at 2:43 PM Sunil K Pandey <skpgkp2@gmail.com> wrote:
>
> This patch disable libmvec math tests if multiarch not enabled.
>
> This fixes [BZ# 28869]
> ---
>  sysdeps/x86_64/fpu/Makefile | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/sysdeps/x86_64/fpu/Makefile b/sysdeps/x86_64/fpu/Makefile
> index 9fb587cf8f..8278ce104a 100644
> --- a/sysdeps/x86_64/fpu/Makefile
> +++ b/sysdeps/x86_64/fpu/Makefile
> @@ -24,6 +24,8 @@ libmvec-support += \
>      $(addprefix svml_s_,$(addsuffix $(l),$(libmvec-funcs))))
>  endif
>
> +# Do not run libmvec tests if multiarch not enabled.
> +ifneq ($(multi-arch),no)
>  # Variables for libmvec tests.
>  ifeq ($(subdir)$(build-mathvec),mathyes)
>  libmvec-tests += double-vlen2 double-vlen4 double-vlen4-avx2 \
> @@ -112,3 +114,4 @@ $(objpfx)bench-double-%.c: $(bench-libmvec-deps)
>         $(PYTHON) $(..)sysdeps/x86_64/fpu/scripts/bench_libmvec.py $(basename $(@F)); } > $@-tmp
>         mv -f $@-tmp $@
>  endif
> +endif
> --
> 2.34.1
>

LGTM.

Reviewed-by: H.J. Lu <hjl.tools@gmail.com>

Thanks.

-- 
H.J.

      reply	other threads:[~2022-02-23 22:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 22:42 Sunil K Pandey
2022-02-23 22:54 ` H.J. Lu [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

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

  git send-email \
    --in-reply-to='CAMe9rOqiUyx3vDCFcfLWTN-Tx=YgqvJJsS1fQ3hG910cj16hwA@mail.gmail.com' \
    --to=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).