public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "romain.geissler at amadeus dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug build/26823] FAIL: elf/tst-cpu-features-cpuinfo with recent trunk: HAS_CPU_FEATURE (ERMS) Date: Wed, 03 Feb 2021 06:09:47 +0000 [thread overview] Message-ID: <bug-26823-131-9wXsj6kKf3@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-26823-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=26823 --- Comment #2 from Romain Geissler <romain.geissler at amadeus dot com> --- Hi, I have now tried with the released glibc 2.33 and still see this issue. H.J., it looks like similar issues were posted on the list here https://sourceware.org/pipermail/libc-alpha/2021-February/122227.html, so is there anything which should be done to fix the ERMS case as well ? Cheers, Romain -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-02-03 6:09 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-30 21:29 [Bug libc/26823] New: " romain.geissler at amadeus dot com 2020-10-30 21:31 ` [Bug build/26823] " romain.geissler at amadeus dot com 2020-12-05 14:12 ` romain.geissler at amadeus dot com 2021-02-03 6:09 ` romain.geissler at amadeus dot com [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=bug-26823-131-9wXsj6kKf3@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@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: linkBe 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).