public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Martin.Jansa at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/29454] dl-cache.c:513: undefined reference to `strcpy' with -Og or -O1 (doesn't happen with -O2)
Date: Sun, 07 Aug 2022 14:36:27 +0000 [thread overview]
Message-ID: <bug-29454-131-qvuDcd3RoX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29454-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29454
--- Comment #1 from Martin Jansa <Martin.Jansa at gmail dot com> ---
diffoscope output when comparing elf/dl-cache.os built with -Og and O2.
| /usr/src/debug/glibc/2.36-r0/git/elf/dl-cache.c:513
│ - call 881 <_dl_load_cache_lookup+0xa1>
│ - R_X86_64_PLT32 memcpy-0x4
│ - mov %rax,%rdi
│ + mov %rbx,%rsi
│ + mov %r12,%rdi
│ + call 7c9 <_dl_load_cache_lookup+0xaa>
│ + R_X86_64_PLT32 strcpy-0x4
│ /usr/src/debug/glibc/2.36-r0/git/elf/dl-cache.c:514
│ - call 889 <_dl_load_cache_lookup+0xa9>
│ + mov %r12,%rdi
│ + call 7d1 <_dl_load_cache_lookup+0xb2>
│ R_X86_64_PLT32 __strdup-0x4
And then it's also reproducible with dl-cache.os rebuilt using "-O2
-fno-builtin-strcpy"
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-08-07 14:36 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-07 13:50 [Bug build/29454] New: " Martin.Jansa at gmail dot com
2022-08-07 13:51 ` [Bug build/29454] " Martin.Jansa at gmail dot com
2022-08-07 14:36 ` Martin.Jansa at gmail dot com [this message]
2022-08-07 14:43 ` goldstein.w.n at gmail dot com
2022-08-07 14:44 ` goldstein.w.n at gmail dot com
2022-08-07 15:00 ` Martin.Jansa at gmail dot com
2022-08-07 15:05 ` goldstein.w.n at gmail dot com
2022-08-07 15:12 ` Martin.Jansa at gmail dot com
2022-08-07 15:13 ` Martin.Jansa at gmail dot com
2022-08-07 15:26 ` goldstein.w.n at gmail dot com
2022-08-07 15:28 ` goldstein.w.n at gmail dot com
2022-08-07 15:28 ` goldstein.w.n at gmail dot com
2022-08-07 15:38 ` Martin.Jansa at gmail dot com
2022-08-07 15:38 ` Martin.Jansa at gmail dot com
2022-08-07 15:39 ` Martin.Jansa at gmail dot com
2022-08-07 15:39 ` Martin.Jansa at gmail dot com
2022-08-07 15:56 ` goldstein.w.n at gmail dot com
2022-08-07 15:56 ` goldstein.w.n at gmail dot com
2022-08-07 16:03 ` Martin.Jansa at gmail dot com
2022-08-07 16:07 ` goldstein.w.n at gmail dot com
2022-08-07 19:39 ` hjl.tools at gmail dot com
2022-08-08 2:52 ` goldstein.w.n at gmail dot com
2022-08-08 3:27 ` goldstein.w.n at gmail dot com
2022-08-08 10:27 ` yann at droneaud dot fr
2022-08-08 19:59 ` sam at gentoo dot org
2022-08-09 10:16 ` goldstein.w.n at gmail dot com
2022-08-09 14:49 ` hjl.tools at gmail dot com
2022-08-09 14:51 ` Martin.Jansa at gmail dot com
2022-08-11 15:33 ` goldstein.w.n 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-29454-131-qvuDcd3RoX@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).