public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stanshebs at earthlink dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27220] Migrate away from nested functions Date: Thu, 21 Jan 2021 18:23:42 +0000 [thread overview] Message-ID: <bug-27220-131-nHbZYL5dZP@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27220-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27220 Stan Shebs <stanshebs at earthlink dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |stanshebs at earthlink dot net --- Comment #2 from Stan Shebs <stanshebs at earthlink dot net> --- The google/grte/v5-2.27/master branch has the necessary code, and it's in production use at Google, so we have some confidence in its correctness. :-) The essence of the dynamic linking change is to pass the bootstrap map as an argument. Not too complicated, but there is a messy aspect in that every elf_machine_rela in sysdeps needs an additional argument. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-01-21 18:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-20 19:33 [Bug dynamic-link/27220] New: " i at maskray dot me 2021-01-20 20:04 ` [Bug dynamic-link/27220] " carlos at redhat dot com 2021-01-21 18:23 ` stanshebs at earthlink dot net [this message] 2021-01-21 19:39 ` carlos at redhat dot com 2021-01-22 14:21 ` tbaeder at redhat dot com 2021-08-23 4:37 ` i at maskray dot me 2022-04-12 17:55 ` carlos at redhat dot com 2023-04-13 20:22 ` carlos at redhat dot com 2023-04-13 20:37 ` adhemerval.zanella at linaro dot org 2023-04-13 23:02 ` i at maskray dot me
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-27220-131-nHbZYL5dZP@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).