(adding libtool-patc...@gnu.org)
Is this guaranteed to work for all versions of the PGI compiler? I.e., does
"pgCC -V" always return something in the form of (digit)+\. ?
On May 17, 2011, at 8:52 PM, Larry Baker wrote:
> This bug applies to OpenMPI 1.4.x and 1.5.x.
>
> The libtool.m4 in conf
Hmm. This sounds right, but I'm a little curious as to why this never came up
before. What was the specific problem that caused you to add this patch?
On May 17, 2011, at 9:41 PM, Larry Baker wrote:
> This bug applies to OpenMPI 1.4.x and 1.5.x.
>
> Inline assembly does not work for PGI comp
Jeff,
Is this guaranteed to work for all versions of the PGI compiler?
I.e., does "pgCC -V" always return something in the form of (digit)+
\. ?
I don't know, but I think so. See your Nov 2009 discussion of this
bug and Ralf Wildenhues' libtool.m4 patches at http://www.open-mpi.org/commu
Below is a sampling of "pgCC -V" outputs in response to Jeff's question.
The complete output looks like:
$ pgCC -V
pgCC 11.1-0 64-bit target on x86-64 Linux -tp nehalem
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2011, STMicroelectronics, Inc. All Rights R
Here is the 'pgCC -V' output from versions that I have access to.
$ pgCC -V
pgCC 7.1-6 64-bit target on x86-64 Linux -tp gh-64
Copyright 1989-2000, The Portland Group, Inc. All Rights Reserved.
Copyright 2000-2007, STMicroelectronics, Inc. All Rights Reserved.
$ pgCC -V
pgCC 9.0-3 64-bit ta
Jeff,Hmm. This sounds right, but I'm a little curious as to why this never came up before.I reported this, as well as several others, in August 2010, "Fixes to OpenMPI-1.4.2 for PGI compilers". (Attached are my patches for OpenMPI 1.4.2.) At that time I was using the PGI 10.x compilers.What was
The PGI compilers have a -fast and a -fastsse option. Does OpenMPI
make effective/safe use of SSE instructions (block moves maybe?)? On
their web site, PGI uses -fast in their examples for OpenMPI rather
than -fastsse. I don't know why.
Larry Baker
US Geological Survey
650-329-5608
ba...
