public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "caiyinyu at loongson dot cn" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30183] New: x86 bug about glibc.cpu.hwcaps processing in ld.so
Date: Wed, 01 Mar 2023 09:03:46 +0000	[thread overview]
Message-ID: <bug-30183-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=30183

            Bug ID: 30183
           Summary: x86 bug about glibc.cpu.hwcaps processing in ld.so
           Product: glibc
           Version: 2.37
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: dynamic-link
          Assignee: unassigned at sourceware dot org
          Reporter: caiyinyu at loongson dot cn
  Target Milestone: ---

x86: Fix bug about glibc.cpu.hwcaps.

    1. export GLIBC_TUNABLES=glibc.cpu.hwcaps=-AVX512
    2. Add  _dl_printf("p -- %s\n", p); just before switch(nl) in
       sysdeps/x86/cpu-tunables.c
    3. compiled and run ./testrun.sh /usr/bin/ls
    you will get:

    p -- -AVX512
    p -- LC_ADDRESS=en_US.UTF-8
    p -- LC_NUMERIC=C
    ...

    The function, TUNABLE_CALLBACK (set_hwcaps)
    (tunable_val_t *valp), checks far more than it should and it
    should stop at end of "-AVX512".

This can be fixed by the following patch.
https://sourceware.org/pipermail/libc-alpha/2023-March/145961.html

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-03-01  9:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01  9:03 caiyinyu at loongson dot cn [this message]
2024-05-01 18:08 ` [Bug dynamic-link/30183] " adhemerval.zanella at linaro dot org

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-30183-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: 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).