public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joerg Faschingbauer <jfasch@aon.at>
To: charlet@ACT-Europe.FR
Cc: jfasch@aon.at, rth@redhat.com, gcc@gcc.gnu.org
Subject: Re: Use of -fPIC on Tru64
Date: Tue, 18 Dec 2001 12:12:00 -0000	[thread overview]
Message-ID: <20011218205324C.jfasch@aon.at> (raw)
In-Reply-To: <20011218001347.B6541@dublin.int.act-europe.fr>

> > The Linux dynamic loader implements loading non-PIC code. What you
> > lose though is sharing of text pages because text has to be patched
> > then.
> 
> What does this have to do with Tru64 where position independent code is part
> of the ABI ?
> 
> I appreciate and understand the motivation on systems such as Linux, but
> Tru64 is very different in this respect, and I still haven't seen a good
> argument to enable -fPIC on Tru64 for libgcc.

The message I replied to was something along "There are
implementations where you do not need PIC to load a shared library, so
there is no need to require PIC". You didn't say anything about Tru64
(though you did in a previous message), and I was nitpicking. Kind of.

Joerg

  reply	other threads:[~2001-12-18 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-13  1:35 Arnaud Charlet
2001-12-13  1:44 ` Richard Henderson
2001-12-13  3:35   ` Arnaud Charlet
2001-12-13  9:26     ` Richard Henderson
2001-12-13  9:40       ` Arnaud Charlet
2001-12-13  9:49         ` Richard Henderson
2001-12-13  9:57           ` Arnaud Charlet
2001-12-17 11:54             ` Joerg Faschingbauer
2001-12-17 15:22               ` Arnaud Charlet
2001-12-18 12:12                 ` Joerg Faschingbauer [this message]
2001-12-18 14:03                   ` Arnaud Charlet
2001-12-18 12:45                 ` Jeff Sturm

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=20011218205324C.jfasch@aon.at \
    --to=jfasch@aon.at \
    --cc=charlet@ACT-Europe.FR \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.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).