public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chethan Palakshamurthy <pchethan@gmail.com>
To: gcc-help@gcc.gnu.org
Subject: Re: Regarding GOT table in PIC code
Date: Tue, 10 Jan 2012 17:36:00 -0000	[thread overview]
Message-ID: <CAASvCC0XZ5A8YcQ4EzRP5jpVASKK1zQ2FFx0Xgix8PqZs_GZBA@mail.gmail.com> (raw)

>> 1. Does the dynamic linker map the physical pages for .data segments
>> such that GOT is at a fixed offset from code in logical address space?
>> is this true?
>
>Yes, it has to do this or it wouldn't be possible to find the GOT.

So, this method of paging is what makes it possible to share code
pages across processes? Several sources online(/books) mention that
PIC is the one which make code sharing across processes possible.

- Chethan

             reply	other threads:[~2012-01-10 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 17:36 Chethan Palakshamurthy [this message]
2012-01-10 17:43 ` Ian Lance Taylor
2012-01-11  8:18   ` Chethan Palakshamurthy
  -- strict thread matches above, loose matches on Subject: below --
2012-01-09 10:47 Chethan Palakshamurthy
2012-01-09 11:17 ` Andrew Haley

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=CAASvCC0XZ5A8YcQ4EzRP5jpVASKK1zQ2FFx0Xgix8PqZs_GZBA@mail.gmail.com \
    --to=pchethan@gmail.com \
    --cc=gcc-help@gcc.gnu.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: 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).