From: Rafael Avila de Espindola <rafael.espindola@gmail.com>
To: David Edelsohn <dje.gcc@gmail.com>,
Binutils Development <binutils@sourceware.org>
Cc: Alan Modra <amodra@gmail.com>,
Florian Weimer <fweimer@redhat.com>,
Cary Coutant <ccoutant@gmail.com>,
Sriraman Tallam <tmsriram@google.com>,
gnu-gabi@sourceware.org, Xinliang David Li <davidxl@google.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>,
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: <8737cosnym.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <CAGWvnynFwXFGLj3tAVgDatn0zmuHcWHyRNuDvR+wRZCXLnar_A@mail.gmail.com>
Where is it documented?
Thanks,
Rafael
David Edelsohn <dje.gcc@gmail.com> writes:
> AIX uses relative relocations and generates position independent
> executables by default. The design of the AIX linker might provide
> some additional inspiration.
>
> Thanks, David
next parent reply other threads:[~2017-05-01 13:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGWvnynFwXFGLj3tAVgDatn0zmuHcWHyRNuDvR+wRZCXLnar_A@mail.gmail.com>
2017-01-01 0:00 ` Rafael Avila de Espindola [this message]
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 ` 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
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 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 ` Florian Weimer
2017-01-01 0:00 ` Alan Modra
2017-01-01 0:00 ` Markus Trippelsdorf
2017-01-01 0:00 ` Sriraman Tallam
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` H.J. Lu
2017-01-01 0:00 ` Sriraman Tallam
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=8737cosnym.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me \
--to=rafael.espindola@gmail.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=ccoutant@gmail.com \
--cc=davidxl@google.com \
--cc=dje.gcc@gmail.com \
--cc=fweimer@redhat.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=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).