Re: [OMPI devel] 1.4.4rc2 is up

[Paul H. Hargrove]

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 Reserved.

Including the initial blank line.

Here is the "important" line for a range of versions I can currently access:

pgCC 7.2-5 64-bit target on x86-64 Linux -tp gh-64
pgCC 8.0-6 64-bit target on x86-64 Linux -tp gh-64
pgCC 9.0-3 64-bit target on x86-64 Linux -tp nehalem-64
pgCC 10.8-0 64-bit target on x86-64 Linux -tp nehalem-64
pgCC 11.1-0 64-bit target on x86-64 Linux -tp nehalem

I am afraid my system w/ 5.x and 6.x versions was retired last month 
(not joking).
However, I found the following output for the C (not C++) compiler in my 
bug database:

pgcc 6.0-8 32-bit target on x86-64 Linux

And for their MacOSX port, there is a wrinkle.  As anybody who as dealt 
w/ mpicc vs mpiCC knows, Apple's filesystem  is case PRESERVING but 
case-insensitive.  So, there PGI's C++ compiler is "pgcpp" and the -V 
output (also from my bug database) looks like:

pgcpp 7.1-5 64-bit target on Apple OS/X


-Paul


On 5/18/2011 5:50 AM, Jeff Squyres wrote:
> (address@hidden)
>
> 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)+\. ?

--
Paul H. Hargrove                          address@hidden
Future Technologies Group
HPC Research Department                   Tel: +1-510-495-2352
Lawrence Berkeley National Laboratory     Fax: +1-510-486-6900