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 libc/26203] New: GLRO(dl_x86_cpu_features) may not be intialized Date: Sat, 04 Jul 2020 12:32:50 +0000 [thread overview] Message-ID: <bug-26203-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=26203 Bug ID: 26203 Summary: GLRO(dl_x86_cpu_features) may not be intialized Product: glibc Version: 2.32 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Target: i386, x86-64 This patch: diff --git a/sysdeps/x86/cacheinfo.c b/sysdeps/x86/cacheinfo.c index 311502dee3..3ddc7104f4 100644 --- a/sysdeps/x86/cacheinfo.c +++ b/sysdeps/x86/cacheinfo.c @@ -769,6 +769,8 @@ init_cacheinfo (void) unsigned int threads = 0; const struct cpu_features *cpu_features = __get_cpu_features (); + assert (cpu_features->basic.kind != arch_kind_unknown); + if (cpu_features->basic.kind == arch_kind_intel) { data = handle_intel (_SC_LEVEL1_DCACHE_SIZE, cpu_features); caused: FAIL: elf/tst-libc_dlvsym-static GLRO(dl_x86_cpu_features) in ld.so is initialized by init_cpu_features, which is invoked by DL_PLATFORM_INIT from _dl_sysdep_start. But ld.so loaded by static executable never calls _dl_sysdep_start. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-07-04 12:32 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-04 12:32 hjl.tools at gmail dot com [this message] 2020-07-04 15:23 ` [Bug libc/26203] " hjl.tools at gmail dot com 2020-10-16 23:54 ` hjl.tools at gmail 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-26203-131@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).