From: Vineet Gupta <vineet.gupta@linux.dev>
To: Florian Weimer <fweimer@redhat.com>,
Vineet Gupta via Libc-help <libc-help@sourceware.org>
Subject: glibc ifunc debug (was Re: glibc tunables to disable axv not updating memcpy)
Date: Wed, 4 Jan 2023 16:04:17 -0800 [thread overview]
Message-ID: <4b4c115d-1ff5-75ab-bc52-c79e81a6f5ec@linux.dev> (raw)
In-Reply-To: <87bkoejnyq.fsf@oldenburg.str.redhat.com>
On 12/8/22 00:31, Florian Weimer wrote:
> * Vineet Gupta via Libc-help:
>
>> Hi,
>>
>> I've been playing with x86_64 tunables to see how they are plumbed
>> into ifunc machinery, but running into a something which I don't
>> understand (this is glibc 2.35 so pretty recent).
>>
>> I'm disabling AVX and friends as:
>> export
>> GLIBC_TUNABLES=glibc.cpu.hwcaps=--SSSE3,-SSE4_2,AVX,-AVX2,-AVX512F,-AVX512VL
>>
>>
>> A simple program which calls memcpy, seems to be calling
>> __memmove_evex_unaligned_erms() despite my tunable disabling AVX512VL.
>>
>> |
>> | main (argc=2, argv=0x7fffffffdce8) at test-mcpu.c:10
>> | 10 memcpy(dest, src, atoi(argv[1]));
>> | (gdb) s
>> | __memmove_evex_unaligned_erms () at
>> ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:307
>> | 307 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S
>>
>>
>> glibc dependency on AVX512VL for the said routine/
>>
>> | IFUNC_IMPL_ADD (array, i, memmove,
>> | CPU_FEATURE_USABLE (AVX512VL),
>> | __memmove_evex_unaligned_erms)
>> |
> This is for the test suite and the benchmarks. The production selector
> is in sysdeps/x86_64/multiarch/ifunc-memmove.h. You should be able to
> set a line-based breakpoint and single-step through it.
Unfortunately gdb doesn't want to put a breakpoint in the ifunc header.
I tried a -g3 -O2 build and excellent tips at [1] - Ubuntu 22.04 - gdb 12.1
| gdb elf/ld-linux-x86-64.so.2
| set exec-wrapper env LD_LIBRARY_PATH=....
| b _start
| ..
| b sysdeps/x86_64/multiarch/ifunc-memmove.h:48
| No source file named sysdeps/x86_64/multiarch/ifunc-memmove.h
| b ../sysdeps/x86_64/multiarch/ifunc-memmove.h:48
It does seem to recognize other headers in x86_64.
Do I need a newer gdb ? Also can't build glibc with -O0 anyways.
Thx,
-Vineet
[1] https://sourceware.org/glibc/wiki/Debugging/Development_Debugging
prev parent reply other threads:[~2023-01-05 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 3:47 glibc tunables to disable axv not updating memcpy Vineet Gupta
2022-12-08 8:31 ` Florian Weimer
2023-01-05 0:04 ` Vineet Gupta [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=4b4c115d-1ff5-75ab-bc52-c79e81a6f5ec@linux.dev \
--to=vineet.gupta@linux.dev \
--cc=fweimer@redhat.com \
--cc=libc-help@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).