public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: libc.so.6: CPU ISA level is lower than required
Date: Wed, 3 Feb 2021 13:32:51 -0800	[thread overview]
Message-ID: <CAMe9rOrprOhzUrWZSJ5qkzCmHLB4_vG_kcZcouqVT8h3A3QkTg@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1so_KYF73jLiwNZO9V96FyneujzC-fUvqAh3d44dLaOZhA@mail.gmail.com>

On Wed, Feb 3, 2021 at 12:17 PM Khem Raj via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Hi All
>
> In Yocto we use -march=core2 to compile glibc and rest of system for
> x86_64 and after upgrading to 2.33, we are seeing an error
>
> /lib/libc.so.6: CPU ISA level is lower than required
>
> when executing the binaries on qemu with -cpu core2duo option, this
> works out ok If I use
> -cpu Nehalem or newer.
>
> I know ldso in 2.33 has got new hwcaps features to check the x86 ISA
> and perhaps thats causing it
> but I am trying to find why would it reject -cpu core2duo from qemu
> when we also ensured
> that -march and -mtune values stay at core2 when compiling glibc and
> rest of system.
>
> I was looking at
>
> https://sourceware.org/git/?p=glibc.git;a=commit;h=ecce11aa0752735c4fd730da6e7c9e0b98e12fb8
>
> since that seems to be the cause and checking if there was some option
> to configure it out.
> I wonder if there is minimal ISA default now which is newer than core2 perhaps ?
>
> I am looking for some help on how can we get to this point and what is
> the right way forward.
>
> Thanks
> -Khem

https://sourceware.org/pipermail/libc-alpha/2021-February/122297.html

-- 
H.J.

      reply	other threads:[~2021-02-03 21:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 19:50 Khem Raj
2021-02-03 21:32 ` 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=CAMe9rOrprOhzUrWZSJ5qkzCmHLB4_vG_kcZcouqVT8h3A3QkTg@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=raj.khem@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).