public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
	 Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: glibc 2.35 failures in elf/tst-cpu-features-cpuinfo-static.
Date: Fri, 14 Jan 2022 22:11:27 +0100	[thread overview]
Message-ID: <87ilumowe8.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <51c4a93d-ab7d-f56d-0ac3-0c0a2b287e9a@redhat.com> (Carlos O'Donell's message of "Fri, 14 Jan 2022 16:09:42 -0500")

* Carlos O'Donell:

> Can we make our testing detect this and mark the test XFAIL?

If we treat this as our bug, we'd have to run CPUID on *all* CPUs during
glibc startup.  The bug is visible to applications as well.  I don't
think this is feasible.

> Or as HJ say, blacklist the CPU from the test e.g. UNSUPPORTED?

I think the bug isn't CPU-specific.

Thanks,
Florian


  reply	other threads:[~2022-01-14 21:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 16:43 Carlos O'Donell
2022-01-14 17:00 ` Florian Weimer
2022-01-14 18:05   ` H.J. Lu
2022-01-14 18:13     ` Florian Weimer
2022-01-14 21:09       ` Carlos O'Donell
2022-01-14 21:11         ` Florian Weimer [this message]
2022-01-14 22:10           ` Carlos O'Donell
2022-01-14 22:23             ` Florian Weimer
2022-01-14 22:30               ` Carlos O'Donell

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=87ilumowe8.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=hjl.tools@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).