PGI Release 2011 Information
- What new features are in the latest release?
- What are the latest release versions?
- What new features have been added to the latest release versions?
- How do I get the latest release?
- How do I find out if my license will work with the current release?
- How do I find out if I qualify for a current release license?
- What is a subscription?
- How does this release differ from the previous release?
- Any known problems with the current releases?
- What problems have been fixed in this release?
PGI 2011 Features and Performance
- PGI Accelerator x64+GPU native Fortran 2003 and C99 compilers now support the full PGI Accelerator Programming Model v1.2 specification for directive-based GPU programming and optimization
- Device-resident data using MIRROR, REFLECTED, UPDATE directives
- Automatic GPU-side loop unrolling; support for the UNROLL clause
- Support for Accelerator regions nested within OpenMP parallel regions
- CUDA Fortran extensions supported in the PGI® 2011 Fortran 2003 compiler enable explicit CUDA GPU programming
- CUDA Fortran module data sharing
- !$CUF KERNEL directive to automate CUDA kernel generation
- Optimized array slice assignments
- CUDA Fortran SDK 1.0 source code examples
- Full support for Fortran 2003
- C/C++ compiler enhancements include the latest EDG release 4.1 front-end with enhanced GNU and Microsoft compatibility, extern inline support, improved BOOST support, thread-safe exception handling
- Compiler optimizations and enhancements include support for AVX code generation, C++ inlining and executable size improvements
- PGPROF® parallel MPI/OpenMP CPU and GPU performance analysis and tuning tool
- Uniform cross-platform performance profiling without re-compiling or any special software privileges on Linux, MacOS and Windows
- PGI Accelerator and CUDA Fortran GPU-side performance statistics
- Updated graphical user interface
- Latest Operating Systems supported including RHEL 5.5, Fedora 12 and Ubuntu 10.04
- Updated and expanded documentation including the PGI Compiler User's Guide, PGI Compiler Reference Manual, PGDBG® Debugger Guide, PGPROF Profiler Guide, PVF® User's Guide and PVF Reference Manual
Complete details are included in the PGI Release Notes and the PGI Visual Fortran® Release Notes.
What are the latest release versions?
The current PGI 2011 release versions are:
PGI Workstation and PGI Server for Linux | 11.10, released October 28, 2011 | ||
PGI CDK® for Linux | 11.10, released October 28, 2011 | ||
PGI Workstation and PGI Server for Windows | 11.10, released October 28, 2011 | ||
PGI Visual Fortran for Windows | 11.10, released October 28, 2011 | ||
PGI CDK for Windows | 11.10, released October 28, 2011 | ||
PGI Workstation for Mac OS X | 11.10, released October 28, 2011 |
Download the current release or download an older release from the PGI archive.
How do I get the latest release?
PGI products are available in the download section. There is also a link after you log in to your account.
How do I find out if my license will work with the current release?
Previously, a PGI license file had a field with 3.000, 3.100, 3.200, 3.300, 4.000, 4.100, 5.000, 5.100, 5.200, 6.000, 6.100, 6.200, 7.000, 7.100, 7.200, 8.000, 9.000 or 10.2 in it. This number represents the highest release this license will support along with all previous releases. (Note: Since 7.0, licenses are compatible with releases back to 5.1—older releases may need the older license format).
With the PGI 2010 release version 10.3, PGI license files use a form of your subscription expiration date as the release number. These licenses will work with any software that is issued before this expiration date. For example, a license with a subscription expiration date of December 25, 2010, will include "2010.1225" as the version in the license.dat file. A new PGI compiler release issued, for example, on June 9, 2010, and called version 10.6, will work with any license that has a subscription date of 2010.0601, or the first day of June 2010. The new compiler releases will work with any license that expires on the first day of the release month, or any date after that. Old releases also work with a new license format because their release version "date" (e.g. 7.200) is also 'before' the subscripton expriration date of 2010.1225.
How do I find out if I qualify for a current release license?
Your subscription information is summarized on your PIN management page. Click any PIN in the list for information about that PIN including subscription expiration date, release number and current license keys. Note that current release licenses use the expiration date of the subscription as the date of the newest release the license will support. If your subscription is current you will not need to generate a new license for a new release. A release for example, 10.5, which came out May 8, 2010, has a release version date of 2010.0501 (the first day of May). A license with subscription expiration date of June 14, 2011, will have a license with a FEATURE or PACKAGE line value of 2011.0614. This license should work with the 10.5 release, along with all releases that are released on or before June 30, 2010.
What is a subscription?
The PGI Subscription Service entitles the subscriber to new licenses for new releases. Typically, a subscription is valid for one year from date of purchase. New license purchases include 60 days of subscription service. If you did not purchase a subscription when you purchased your license, or if your subscription has expired, you can qualify for the current relase by bringing your subscription current. You may also wish to read the PGI Subscription Service Agreement.
How does this release differ from the previous release?
- PGI 2011 includes full support for Fortran 2003.
- Further information can be found in the PGI 2011 Release Notes located in the documentation section.
Any known problems with the recent releases?
- 32-bit executables that use libpthreads may fail on 64-bit Linux systems because libpthreads reduces stack size to 2MB. This is a Linux limitation. libpthreads is used by routines compiled -mp or -Mconcur. 64-bit executables do not experience this limitation.
- Some users linking with libpthreads (-mp or -Mconcur) have seen the error message symbol _h_errno, version GLIBC_2.2.5 not defined in file libc.so.6 with link time reference This can be worked around with the environment variable LD_ASSUME_KERNEL export LD_ASSUME_KERNEL=2.4.1 or export LD_ASSUME_KERNEL=2.2.5 for example.