On Wed, Jul 26, 2017 at 1:57 PM, David Olsen via Boost wrote:

I have created six pull requests that make it possible to build Boost with PGI.

That is wonderful! Just wondering, how will the move to CMake affect your use-case? Thanks

On 7/26/17 13:57, David Olsen via Boost wrote:

Many years ago, Boost was configured to work well with the PGI C++ compiler (http://www.pgroup.com/). But maintenance of the PGI support within Boost stopped about five years ago, and PGI will no longer build Boost without modifications to the Boost sources.

I am working on restoring support for the PGI C++ compiler. Many PGI customers want to use Boost, so we at PGI are putting in the effort to make that easy to do. I have already fixed a bunch of bugs in the PGI compiler that were triggered by Boost code. Now it is time to make necessary adjustments to the Boost source.

Hi David - The PGI C++ compiler is not represented by any of the test configurations. Would you be willing to host test runners so that the test matrix [1] reflects the PGI status? michael [1] http://www.boost.org/development/tests/develop/developer/summary.html -- Michael Caisse Ciere Consulting ciere.com

Hi David,

On Jul 26, 2017, at 2:57 PM, David Olsen via Boost wrote:

Many years ago, Boost was configured to work well with the PGI C++ compiler (http://www.pgroup.com/). But maintenance of the PGI support within Boost stopped about five years ago, and PGI will no longer build Boost without modifications to the Boost sources.

As the original developer and maintainer of the PGI toolset, I had no end of problems with compiler termination semantics, excessively long compile times (worse with TMP code), and with poor std support, so that's why Boost PGI support languished. I do hope you’re able to bring PGI into the Boost fold. Welcome aboard!