public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Stefan Liebler <stli@linux.ibm.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH 3/3] s390x: Check HWCAP bits against compiler flags
Date: Wed, 12 May 2021 09:43:23 +0200	[thread overview]
Message-ID: <5e7849a4-fd6d-26fd-e89f-fa385e946e46@linux.ibm.com> (raw)
In-Reply-To: <a9688d1a65abfd24b92120d36e6ccaad51e64d32.1620304013.git.fweimer@redhat.com>

On 06/05/2021 14:30, Florian Weimer via Libc-alpha wrote:
> When compiled with GCC 11.1 and -march=z14 -O3 build flags, running
> ld.so (or any dynamically linked program) prints:
> 
> Fatal glibc error: CPU lacks VXE support (z14 or later required)
> 
> Co-Authored-By: Stefan Liebler <stli@linux.ibm.com>
> ---
>  sysdeps/s390/s390-64/dl-hwcap-check.h | 40 +++++++++++++++++++++++++++
>  1 file changed, 40 insertions(+)
>  create mode 100644 sysdeps/s390/s390-64/dl-hwcap-check.h
> 
> diff --git a/sysdeps/s390/s390-64/dl-hwcap-check.h b/sysdeps/s390/s390-64/dl-hwcap-check.h
> new file mode 100644
> index 0000000000..87e18be6bd
> --- /dev/null
> +++ b/sysdeps/s390/s390-64/dl-hwcap-check.h
> @@ -0,0 +1,40 @@
> +/* Check for hardware capabilities after HWCAP parsing.  S390 version.
> +   Copyright (C) 2021 Free Software Foundation, Inc.
> +   This file is part of the GNU C Library.
> +
> +   The GNU C Library is free software; you can redistribute it and/or
> +   modify it under the terms of the GNU Lesser General Public
> +   License as published by the Free Software Foundation; either
> +   version 2.1 of the License, or (at your option) any later version.
> +
> +   The GNU C Library is distributed in the hope that it will be useful,
> +   but WITHOUT ANY WARRANTY; without even the implied warranty of
> +   MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
> +   Lesser General Public License for more details.
> +
> +   You should have received a copy of the GNU Lesser General Public
> +   License along with the GNU C Library; if not, see
> +   <https://www.gnu.org/licenses/>.  */
> +
> +#ifndef _DL_HWCAP_CHECK_H
> +#define _DL_HWCAP_CHECK_H
> +
> +#include <ldsodefs.h>
> +
> +static inline void
> +dl_hwcap_check (void)
> +{
> +#if defined __ARCH__
> +# if __ARCH__ >= 13
> +  if (!(GLRO(dl_hwcap) & HWCAP_S390_VXRS_EXT2))
> +    _dl_fatal_printf ("\
> +Fatal glibc error: CPU lacks VXRS_EXT2 support (z15 or later required)\n");
> +# elif __ARCH__ >= 12
> +  if (!(GLRO(dl_hwcap) & HWCAP_S390_VXE))
> +    _dl_fatal_printf ("\
> +Fatal glibc error: CPU lacks VXE support (z14 or later required)\n");
> +# endif
> +#endif /* __ARCH__ */
> +}
> +
> +#endif /* _DL_HWCAP_CHECK_H */
> 

Hi Florian,

while running some tests, I got the messages as expected:
on z13:
- "-march=z13" => no message
- "-march=z14" => "z14 or later required"
- "-march=z15" => "z15 or later required"

on z14:
- "-march=z13" => no message
- "-march=z14" => no message
- "-march=z15" => "z15 or later required"

on z15:
- "-march=z13" => no message
- "-march=z14" => no message
- "-march=z15" => no message

Reviewed-by: Stefan Liebler <stli@linux.ibm.com>

Thanks,
Stefan

      reply	other threads:[~2021-05-12  7:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 12:30 [PATCH 0/3] Checking " Florian Weimer
2021-05-06 12:30 ` [PATCH 1/3] elf: Add hook for checking HWCAP bits after auxiliary vector parsing Florian Weimer
2021-05-12  7:43   ` Stefan Liebler
2021-05-06 12:30 ` [PATCH 2/3] powerpc64le: Check HWCAP bits against compiler build flags Florian Weimer
2021-05-11 21:12   ` Lucas A. M. Magalhaes
2021-05-12  8:27     ` Florian Weimer
2021-05-12 14:50       ` Lucas A. M. Magalhaes
2021-05-12 14:52       ` Tulio Magno Quites Machado Filho
2021-05-12 17:27         ` Florian Weimer
2021-05-12 19:24           ` Tulio Magno Quites Machado Filho
2021-05-18 16:59         ` Florian Weimer
2021-05-18 17:26           ` Tulio Magno Quites Machado Filho
2021-05-18 17:41             ` Florian Weimer
2021-05-06 12:30 ` [PATCH 3/3] s390x: Check HWCAP bits against compiler flags Florian Weimer
2021-05-12  7:43   ` Stefan Liebler [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=5e7849a4-fd6d-26fd-e89f-fa385e946e46@linux.ibm.com \
    --to=stli@linux.ibm.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).