[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Libtool strips out -tp=k8-32 PGI compiler flag in link mode
From: |
Ethan Mallove |
Subject: |
Re: Libtool strips out -tp=k8-32 PGI compiler flag in link mode |
Date: |
Thu, 26 Mar 2009 10:17:11 -0500 |
User-agent: |
Mutt/1.5.17 (2007-11-01) |
On Sat, Mar/21/2009 11:47:42AM, Ralf Wildenhues wrote:
> * Ralf Wildenhues wrote on Sat, Mar 21, 2009 at 11:41:20AM CET:
> > Thanks for the bug report. A workaround should be to
> > ./configure CC="pgcc -tp=k8-32"
> >
> > and the following patch should fix the issue. Can you try both?
>
> Never mind; the `-tp PROCESSOR' gets reordered badly by libtool anyway,
> so only `-tp=PROCESSOR' is feasible. Updated patch below. OTOH,
> another workaround should be to pass -Wc,-tp=k8-32 to `libtool
> --mode=link'.
AM_CFLAGS seems to do the trick, e.g.,
$ make AM_CFLAGS='-Wc,-tp=k8-32'
>
> Cheers,
> Ralf
>
> Allow through -tp=* at link time, for pgcc.
>
> * libltdl/config/ltmain.m4sh (func_mode_link): Portlant Group
> pgcc uses `-tp=PROCESSOR' for target processor selection; allow
> the flag through at link time.
> * THANKS: Update.
> Report by Ethan Mallove.
>
> diff --git a/libltdl/config/ltmain.m4sh b/libltdl/config/ltmain.m4sh
> index f17ad72..c122458 100644
> --- a/libltdl/config/ltmain.m4sh
> +++ b/libltdl/config/ltmain.m4sh
> @@ -4497,8 +4497,9 @@ func_mode_link ()
> # -F/path gives path to uninstalled frameworks, gcc on darwin
> # -p, -pg, --coverage, -fprofile-* pass through profiling flag for GCC
> # @file GCC response files
> + # -tp=* Portland pgcc target processor selection
> -64|-mips[0-9]|-r[0-9][0-9]*|-xarch=*|-xtarget=*|+DA*|+DD*|-q*|-m*| \
> - -t[45]*|-txscale*|-p|-pg|--coverage|-fprofile-*|-F*|@*)
> + -t[45]*|-txscale*|-p|-pg|--coverage|-fprofile-*|-F*|@*|-tp=*)
> func_quote_for_eval "$arg"
> arg="$func_quote_for_eval_result"
> func_append compile_command " $arg"
I am using the latest Libtool from the git repo (Fri Mar 20 16:42:25),
with the above "-tp" patch and libtoolize is stuck pegging my CPU at
99%. I assume I should have been applying the "-tp" patch to a stable
Libtool version, e.g., 2.2.6?
Thanks,
Ethan