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@sources.redhat.com Subject: [Bug dynamic-link/14538] New: Complicated x86-64 elf_machine_dynamic/elf_machine_load_address Date: Sat, 01 Sep 2012 05:00:00 -0000 [thread overview] Message-ID: <bug-14538-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14538 Bug #: 14538 Summary: Complicated x86-64 elf_machine_dynamic/elf_machine_load_address Product: glibc Version: 2.17 Status: NEW Severity: normal Priority: P2 Component: dynamic-link AssignedTo: unassigned@sourceware.org ReportedBy: hjl.tools@gmail.com Classification: Unclassified Target: x86-64 x86-64 has /* Return the link-time address of _DYNAMIC. Conveniently, this is the first element of the GOT. This must be inlined in a function which uses global data. */ static inline ElfW(Addr) __attribute__ ((unused)) elf_machine_dynamic (void) { ElfW(Addr) addr; /* This works because we have our GOT address available in the small PIC model. */ addr = (ElfW(Addr)) &_DYNAMIC; return addr; } /* Return the run-time load address of the shared object. */ static inline ElfW(Addr) __attribute__ ((unused)) elf_machine_load_address (void) { ElfW(Addr) addr; /* The easy way is just the same as on x86: leaq _dl_start, %0 leaq _dl_start(%%rip), %1 subq %0, %1 but this does not work with binutils since we then have a R_X86_64_32S relocation in a shared lib. Instead we store the address of _dl_start in the data section and compare it with the current value that we can get via an RIP relative addressing mode. Note that this is the address of _dl_start before any relocation performed at runtime. In case the binary is prelinked the resulting "address" is actually a load offset which is zero if the binary was loaded at the address it is prelinked for. */ asm ("lea _dl_start(%%rip), %0\n\t" "sub 1f(%%rip), %0\n\t" ".section\t.data.rel.ro\n" "1:\t" ASM_ADDR " _dl_start\n\t" ".previous\n\t" : "=r" (addr) : : "cc"); return addr; } while i386 has /* Return the link-time address of _DYNAMIC. Conveniently, this is the first element of the GOT, a special entry that is never relocated. */ static inline Elf32_Addr __attribute__ ((unused, const)) elf_machine_dynamic (void) { /* This produces a GOTOFF reloc that resolves to zero at link time, so in fact just loads from the GOT register directly. By doing it without an asm we can let the compiler choose any register. */ extern const Elf32_Addr _GLOBAL_OFFSET_TABLE_[] attribute_hidden; return _GLOBAL_OFFSET_TABLE_[0]; } /* Return the run-time load address of the shared object. */ static inline Elf32_Addr __attribute__ ((unused)) elf_machine_load_address (void) { /* Compute the difference between the runtime address of _DYNAMIC as seen by a GOTOFF reference, and the link-time address found in the special unrelocated first GOT entry. */ extern Elf32_Dyn bygotoff[] asm ("_DYNAMIC") attribute_hidden; return (Elf32_Addr) &bygotoff - elf_machine_dynamic (); } i386 version is straight forward and easy to understand. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-09-01 5:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-09-01 5:00 hjl.tools at gmail dot com [this message] 2012-09-01 5:11 ` [Bug dynamic-link/14538] " hjl.tools at gmail dot com 2012-09-01 12:49 ` hjl.tools at gmail dot com 2012-09-02 18:09 ` hjl.tools at gmail dot com 2014-06-17 4:47 ` 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-14538-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).