PGI New Release Information
- What new features are in the latest release?
- What are 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?
- Any known problems with the current releases?
- What problems have been fixed in this release?
- PGI Compilers Language Support
- Full Fortran 2003 with CUDA Fortran extensions
- GNU-compatible C++ with all PGI features and optimizations
- Full CUDA C/C++ compiler for targeting multi-core x64
- Multi-core x64 Optimizations
- AVX SIMD vectorization for Intel and AMD CPUs
- IPA optimizations for improved auto-parallelization
- GPU Computing
- Full support for the PGI Accelerator programming model specification v1.3
- Support for the OpenACC GPU programming directives specification v1.0 for F2003 and C99 (beta 12.3, production 12.6)
- Asynchronous data transfers and kernel launch
- PGI Tools
- Remote cluster debugging using PGDBG® GUI on a local client
- Eclipse integration of the PGI C/C++ compilers on Linux
- PGI Unified Binary—Supported across Intel and AMD CPUs and NVIDIA GPUs
- CUDA Fortran—Ability to specify a stream ID in CUF kernels
- Fortran 2003—Support for recursive I/O
- Expanded Operating System Support
- Red Hat Enterprise Linux 6.2
- Fedora 16
- SLES 11 SP1
- Ubuntu 11.10
- Mac OS X Lion
- Updated Documentation
The current PGI 2012 release versions are:
|PGI Workstation and PGI Server for Linux||12.10, released October 28, 2012|
|PGI CDK® for Linux||12.10, released October 28, 2012|
|PGI Workstation and PGI Server for Windows||12.10, released October 28, 2012|
|PGI Visual Fortran for Windows||12.10, released October 28, 2012|
|PGI CDK for Windows||12.10, released October 28, 2012|
|PGI Workstation for Mac OS X||12.10, released October 28, 2012|
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.
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.
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.
- 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.