From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-42754-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 9498 invoked by alias); 13 Dec 2001 09:28:50 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 9476 invoked from network); 13 Dec 2001 09:28:49 -0000
Received: from unknown (HELO dublin.ACT-Europe.FR) (212.157.227.154)
  by sources.redhat.com with SMTP; 13 Dec 2001 09:28:49 -0000
Received: by dublin.ACT-Europe.FR (Postfix, from userid 525)
	id A52E022A0BF; Thu, 13 Dec 2001 10:29:09 +0100 (MET)
Date: Thu, 13 Dec 2001 01:35:00 -0000
From: Arnaud Charlet <charlet@ACT-Europe.FR>
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Use of -fPIC on Tru64
Message-ID: <20011213102908.B10630@dublin.int.act-europe.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-SW-Source: 2001-12/txt/msg00690.txt.bz2

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