Dear PGI support,
There is still an unsolved question about shared library support in PGI
compilers on 64bit platforms.
* Ralf Wildenhues wrote on Wed, May 18, 2005 at 11:35:21AM CEST:
> * Troy Telford wrote on Thu, May 05, 2005 at 09:39:18PM CEST:
> > On Thu, 05 May 2005 11:38:31 -0600, Ralf Wildenhues wrote:
> >
> > >>After running configure, one of the things it appears to generate
> > >>are a few 'libtool' scripts scattered around the source tree.
> > >>
> > >>After running into a few problems where the compiler is telling me I
> > >>need to compile with -fPIC, (but PGI uses both -fpic and -fPIC; so
> > >>whatever). I looked at the actual 'pgcc' invocation. libtool isn't
> > >>invoking pgcc with -fPIC.
> > >
> > >You mean: at link time it isn't. Right?
> >
> > Sure. I'll start where it enters a directory and then starts running
> > 'make'
>
> I changed this in Libtool-1.5.18, based solely on this discussion here.
> Our C++ (tagdemo) tests still fail. I do not know the correct way to
> fix this, PGI support has been informed about the issue but has stayed
> silent so far.
After all, I believe this was not enough.
I can get the Libtool C++ demo to pass on x86_64 when I add the option
-mcmodel=medium
to the compile command lines. It seems that this is necessary when
vtables are used. I am really asking myself why this is not enabled by
default with pgCC? Now I am trying to evaluate whether Libtool should
enable this by itself or whether we should leave this up to the user and
only document it (e.g. because there might be a good reason against
doing so).
Now, I spent quite some time searching the docs for this, and I would
*really* like to know answers to the following questions:
Is it sufficient to pass this to pgCC only, or would pgcc/pgf77/pgf90
need this as well in some circumstances?
Does version 5.x of the PGI compilers need this as well on x86_64?
Regards,
Ralf
|
