From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Use of -fPIC on Tru64
Date: Thu, 13 Dec 2001 01:35:00 -0000 [thread overview]
Message-ID: <20011213102908.B10630@dublin.int.act-europe.fr> (raw)
Hi there,
I was wondering why on Dec Unix/Tru64, GCC now includes -fPIC in
TARGET_LIBGCC2_FLAGS.
This was not the case with GCC 2.8.1, and as far as I understood, position
independent code is part of the ABI. So I guess I am missing something because
I do not understand why -fPIC is specified explicitely.
Could you clarify this issue ?
Arno
next reply other threads:[~2001-12-13 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 1:35 Arnaud Charlet [this message]
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
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=20011213102908.B10630@dublin.int.act-europe.fr \
--to=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).