public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/27201] Consider disabling x86-64-v2 support check
Date: Thu, 21 Jan 2021 15:27:29 +0000 [thread overview]
Message-ID: <bug-27201-131-yT4UOR6LFN@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27201-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27201
--- Comment #18 from H.J. Lu <hjl.tools at gmail dot com> ---
I managed to do it. I got
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 6
model name : QEMU Virtual CPU version 2.5+
stepping : 3
microcode : 0x1
cpu MHz : 3407.984
cache size : 16384 KB
physical id : 0
siblings : 1
core id : 0
cpu cores : 1
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pse36 clflush mmx fxsr sse sse2 syscall nx lm rep_good nopl xtopology cpuid
tsc_known_freq pni cx16 x2apic hypervisor lahf_lm cpuid_fault pti
bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds
swapgs itlb_multihit
bogomips : 6815.96
clflush size : 64
cache_alignment : 64
address sizes : 40 bits physical, 48 bits virtual
power management:
on Skylake.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-21 15:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 14:23 [Bug dynamic-link/27201] New: " fweimer at redhat dot com
2021-01-18 15:35 ` [Bug dynamic-link/27201] " hjl.tools at gmail dot com
2021-01-18 20:47 ` hjl.tools at gmail dot com
2021-01-18 20:51 ` fweimer at redhat dot com
2021-01-18 20:58 ` hjl.tools at gmail dot com
2021-01-18 21:06 ` hjl.tools at gmail dot com
2021-01-18 21:10 ` hjl.tools at gmail dot com
2021-01-18 21:20 ` fweimer at redhat dot com
2021-01-18 21:33 ` hjl.tools at gmail dot com
2021-01-18 23:51 ` hjl.tools at gmail dot com
2021-01-19 11:09 ` fweimer at redhat dot com
2021-01-19 12:34 ` hjl.tools at gmail dot com
2021-01-19 16:56 ` hjl.tools at gmail dot com
2021-01-21 12:45 ` berrange at redhat dot com
2021-01-21 13:00 ` hjl.tools at gmail dot com
2021-01-21 13:58 ` berrange at redhat dot com
2021-01-21 15:12 ` hjl.tools at gmail dot com
2021-01-21 15:17 ` fweimer at redhat dot com
2021-01-21 15:27 ` hjl.tools at gmail dot com [this message]
2021-01-21 15:28 ` hjl.tools at gmail dot com
2021-01-21 15:41 ` fweimer at redhat dot com
2021-01-21 15:56 ` hjl.tools at gmail dot com
2021-01-21 23:34 ` hjl.tools at gmail dot com
2021-01-22 9:44 ` berrange at redhat dot com
2021-01-22 9:59 ` fweimer at redhat dot com
2021-01-22 10:13 ` berrange at redhat dot com
2021-01-22 10:19 ` fweimer at redhat dot com
2021-01-28 17:46 ` fweimer at redhat dot com
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-27201-131-yT4UOR6LFN@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: 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).