From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Sriraman Tallam <tmsriram@google.com>
Cc: gnu-gabi@sourceware.org, binutils <binutils@sourceware.org>,
"Xinliang David Li" <davidxl@google.com>,
"Cary Coutant" <ccoutant@gmail.com>,
"Sterling Augustine" <saugustine@google.com>,
"Paul Pluzhnikov" <ppluzhnikov@google.com>,
"Ian Lance Taylor" <iant@google.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
"Rahul Chaudhry" <rahulchaudhry@google.com>,
"Luis Lozano" <llozano@google.com>,
"Rafael Espíndola" <rafael.espindola@gmail.com>,
"Peter Collingbourne" <pcc@google.com>,
"Rui Ueyama" <ruiu@google.com>
Subject: Re: Reducing code size of Position Independent Executables (PIE) by shrinking the size of dynamic relocations section
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <20170426054636.GB31793@x4> (raw)
In-Reply-To: <CAJimCsFzz1qy9qCcvaMRtgcRv9oNE7C-+3Ku9JcjBGOvqtWrVg@mail.gmail.com>
On 2017.04.25 at 21:06 -0700, Cary Coutant wrote:
> > Idea A: Shrinking the size of the dynamic relocations
>
> In a RELATIVE relocation, the r_offset field is really the only field
> of interest. The symbol and addend are not used -- the dynamic loader
> simply adjusts the address at the given offset by the relocation
> factor for the load module. Thus, it truly is possible to reduce these
> relocations to just the one word.
>
> Simon Baldwin did a lot of work on this a few years ago for Chromium,
> writing a post-link utility to extract all the RELATIVE relocations
> and rewrite them to a new section.
FYI Mike Hommey did something similar for Firefox and wrote about here:
https://glandium.org/blog/?p=1177
--
Markus
next prev parent reply other threads:[~2017-04-26 5:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 Sriraman Tallam
2017-01-01 0:00 ` Rafael Espíndola
2017-01-01 0:00 ` Sriraman Tallam
2017-01-01 0:00 ` Cary Coutant
2017-01-01 0:00 ` Markus Trippelsdorf [this message]
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Alan Modra
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Sriraman Tallam
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Sriraman Tallam
[not found] <CAGWvnynFwXFGLj3tAVgDatn0zmuHcWHyRNuDvR+wRZCXLnar_A@mail.gmail.com>
2017-01-01 0:00 ` Rafael Avila de Espindola
2017-01-01 0:00 ` David Edelsohn
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Suprateeka R Hegde
2017-01-01 0:00 ` Sriraman Tallam via gnu-gabi
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Sriraman Tallam via gnu-gabi
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
[not found] ` <CAORpzuMftCGpXUObOyoFY0=jorMBDWEDbQJ23DifTNW3v-WA6Q@mail.gmail.com>
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
2017-01-01 0:00 ` Cary Coutant
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
[not found] ` <CAORpzuPYsSBJtypm3NDcfcgRzos3WO4JjkvgiqpyBYBhoqLVFA@mail.gmail.com>
2018-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Cary Coutant
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
2017-01-01 0:00 ` Rahul Chaudhry via gnu-gabi
2017-01-01 0:00 ` Ian Lance Taylor via gnu-gabi
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=20170426054636.GB31793@x4 \
--to=markus@trippelsdorf.de \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=davidxl@google.com \
--cc=gnu-gabi@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=iant@google.com \
--cc=llozano@google.com \
--cc=pcc@google.com \
--cc=ppluzhnikov@google.com \
--cc=rafael.espindola@gmail.com \
--cc=rahulchaudhry@google.com \
--cc=ruiu@google.com \
--cc=saugustine@google.com \
--cc=tmsriram@google.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.
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).