10.4.0 B27

This build was release on January 10, 2018.

Asminst

Due to issues with the newly-introduced optimizations for

The --one_instantiation_per_object object mode is disabled by default. This change is related to issues introduced by ppc_ghs_4_2, ppc_ghs_4_0, and ppc_ghs_3_5 optimizations.

Run the --enable-prelink-optimization option to enable the --one_instantiation_per_object object mode.

10.4.0 B20

This build was released on January 5, 2018.

Asminst

• Added support for --one_instantiation_per_object with the ppc_ghs_2017_1 compiler.
• Performance improvements for --one_instantiation_per_object with the ppc_ghs_4_2, ppc_ghs_4_0, and ppc_ghs_3_5 compilers when several template instantiations must be compiled at link time. The ppc_ghs_2017_1 compiler is not affected by the original performance issue occurring with the other versions.
• Introduced the concept of a function whitelist. A blacklist is already supported. Whitelists and blacklists cannot be specified together on the same command line. You can only use a whitelist or a blacklist but not both.
• Support for partial matching with * and ? wildcards has been added for whitelists and blacklists.

10.4.0 B15

This build was released on December 14, 2017.

Asminst

• Renamed ppc_ghs_7_1 compiler acronym to ppc_ghs_2017_1. 

Asminfer

• Improved jump table scanning for ppc_ghs_2017_1

10.4.0 B8

This build was release on December 12, 2017.

Asminst

• Disabled the experimental microcode binary file generation support.

10.4.0 B5

This version was release on December 11, 2017.

Asminst

• Added support for ppc_ghs_7_1 compiler (32-bit only) for C. 
• Added support for ppc_ghs_7_1 compiler (32-bit only) for C++. The --one_instantiation_per_object option, however, is not supported due to changes in how the underlying pre-linking system works. 
• Various modifications have been introduced to the microcode to make it easier to maintain.
• Introduced performance improvements to the various types of microcode for ppc_ghs-based compilers.
• Microcode is now saved to disk in a binary format upon first compilation. The binary file is loaded in place of the plain text microcode upon subsequent loads for a given project. The binary microcode file is stored in the log directory.