mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Huge inefficiency on powerpc due to duplicated GOT
Date: Mon, 25 May 2015 17:57:34 -0400	[thread overview]
Message-ID: <20150525215734.GA9323@brightrain.aerifal.cx> (raw)

The same issue that led to having to reprocess non-GOT/PLT-type
relocations in ldso/libc seems to be making more trouble for us.
ld-musl-powerpc.so.1 contains nearly 2 whole pages of GOT, due to each
translation unit getting its own GOT in the .got2 section (and using
non-GOT reloc types) and having them all concatenated with no merging.
Anyone know what's up with this? Is it a toolchain bug, perhaps
resulting from secure-plt mode not being widely tested? Is there any
workaround?

Rich


                 reply	other threads:[~2015-05-25 21:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20150525215734.GA9323@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=musl@lists.openwall.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).