This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] _GCC_PICFLAG: use -fPIC for s390x targets
- From: Andreas Krebbel <krebbel at linux dot vnet dot ibm dot com>
- To: Rainer Orth <ro at CeBiTec dot Uni-Bielefeld dot DE>
- Cc: Mike Frysinger <vapier at gentoo dot org>, gcc-patches at gcc dot gnu dot org, s390 at gentoo dot org, Aurelien Jarno <aurelien at aurel32 dot net>, Martin Schwidefsky <schwidefsky at de dot ibm dot com>, Ulrich Weigand <uweigand at de dot ibm dot com>, Andreas Krebbel <Andreas dot Krebbel at de dot ibm dot com>
- Date: Tue, 13 Dec 2011 13:02:47 +0100
- Subject: Re: [PATCH] _GCC_PICFLAG: use -fPIC for s390x targets
- References: <1323228983-27811-1-git-send-email-vapier@gentoo.org> <ydd39cwwwsd.fsf@manam.CeBiTec.Uni-Bielefeld.DE>
On 12/07/2011 10:33 AM, Rainer Orth wrote:
> Mike Frysinger <vapier@gentoo.org> writes:
>> s390*-*-*)
>> $1=-fpic
>> ;;
>
> Perhaps it's better to remove both s390* cases and use the -fPIC default
> everywhere, as does libtool. picflag.m4 is supposed to be usable
> everywhere.
>From a performance perspective the "fix after breakage" approach still would make sense
since GCC generates slightly faster code with -fpic compared to -fPIC. On the other hand
the user visible shared libs like libgomp, libgfortran, and libstdc++ are already built
with -fPIC anyway. We recently also enabled -fPIC for libgcc_s.so. And now we are about to
do the same for libiberty. So I think there does not remain much anyway - or am I missing
something?!
So I agree that removing the s390*-*-* case entirely in picflag.m4 will be the better way
to fix this. We then also should revert that one:
http://gcc.gnu.org/ml/gcc-patches/2011-11/msg00643.html
Bye,
-Andreas-