Arm Forge Release History

This page describes the changes between releases of Arm Forge.

To download and install the latest version of Arm Forge, see our downloads page and follow the installation steps given in the Arm Forge user guide.

For more compatibility information, see our Known Issues, Arm DDT supported platforms, and Arm MAP supported platforms topics.

Arm Forge

Version 19.0 - latest update 19.0.5

Released: May 03, 2019

What's new in 19.0 - latest update 19.0.5

Arm Forge 19.0 covers the following releases:

  • Arm Forge 19.0.0 - Released 7th December 2018
  • Arm Forge 19.0.1 - Released 18th December 2018
  • Arm Forge 19.0.2 - Released 25th January 2019
  • Arm Forge 19.0.3 - Released 1st March 2019
  • Arm Forge 19.0.4 - Released 29th March 2019
  • Arm Forge 19.0.5 - Released 3rd May 2019

Arm DDT new features and enhancements:

19.0.0

  • Syntax highlighting for Python is now supported.
  • GDB 8.1 is now available as a choice of debugger.

19.0.1

  • None in this release.

19.0.2

  • Improved recommendations for static linking in the Arm Forge user guide.

19.0.3

  • Items in the variables views can now be sorted by name. Click the title to sort items in the view.

19.0.4

  • None in this release.

19.0.5

  • None in this release.

Arm DDT bug fixes:

19.0.0

  • [FOR-6278] Pretty printer now shows content of a std::shared_ptr in the variable view.
  • [FOR-6257] Fixed an issue where strings containing "..." caused the GUI to crash.
  • [FOR-5802] Fixed an issue where memory alignment was ignored when memory debugging with guard pages was enabled.
  • [FOR-5712] Fixed an issue where unions were falsely classified as an array and could not be inspected.
  • [FOR-5412] You can now launch serial programs that are in the environment's path without specifying the full path.

19.0.1

  • [FOR-6407] Fixed a startup issue with CRAY ALPS.

19.0.2

  • [FOR-6117] Fixed an issue that caused formatting in the variable views to be hidden when selecting elements.
  • [FOR-6527] Fixed an issue in the previous release related to Qt5 pretty printers.
  • [FOR-6601] Fixed the display of complex Fortran structures in the variables views.

19.0.3

  • [FOR-6564] The Known Issues section of the Forge user guide has been updated to describe compilation flags for OpenMPI 3.x with GCC, to fix a startup issue.

19.0.4

  • [FOR-6741] Fixed an issue that prevents the display of process IDs in offline debug logs.
  • [FOR-6703] Fixed an issue that causes a memory debugging deadlock when collecting stack backtraces for memory allocations.

19.0.5

  • [FOR-7131] Fixes an issue which caused sparklines to be rendered incorrectly in DDT offline reports gathered on PowerPC platforms.
  • [FOR-7210] Fixes an issue where Forge could not be launched on some alternative window managers like Fluxbox.
  • [FOR-6988] Fixes an issue when debugging static PGI binaries.
  • [FOR-7106] Fixes an issue where the number of OpenMP threads were not being set correctly when using express launch.
  • [FOR-7094] Fixes an issue where processes launched by srun would have their CPU affinity settings reset.


Arm MAP new features and enhancements:

19.0.0

  • You can now profile Python scripts with Arm MAP. Refer to the 'Python Profiling' chapter in the Arm Forge user guide for further information.
  • Syntax highlighting for Python is now supported.
  • The following limitation that was required in releases prior to 18.0 has been removed from the Forge user guide: "Unwind information is not always compiled in by default on this platform. This may result in partial trace nodes being displayed in the MAP parallel stack view. To avoid this, programs that are not compiled with debug information (-g) should at least be compiled with the -fasynchronous-unwind-tables flag or the -funwind-tables flag, preferably the former."

19.0.1

  • None in this release.

19.0.2

  • None in this release.

19.0.3

  • None in this release.

19.0.4

  • Support for profiling debug versions of Python.

19.0.5

  • None in this release.

Arm MAP bug fixes:

19.0.0

  • [FOR-6217] Fixed an issue that caused a slowdown in MAP's analysis phase.
  • [FOR-5412] You can now launch serial programs that are in the environment's path without specifying the full path.

19.0.1

  • [FOR-6407] Fixed a startup issue with CRAY ALPS.

19.0.2

  • [FOR-6394] Fixed an issue on AArch64 builds, where multiple 'CPU Instructions' metric presets are visible from the Metrics menu.
  • [FOR-6510] Arm MAP can now profile applications when SHELL is unset.

19.0.3

  • [FOR-6564] The Known Issues section of the Forge user guide has been updated to describe compilation flags for OpenMPI 3.x with GCC, to fix a startup issue.

19.0.4

  • [FOR-6722] Fixed an issue that causes extra items to be shown in the Functions view.
  • [FOR-6791] Fixed an issue that causes the incorrect number of physical cores to be reported.
  • [FOR-6825] MAP can now display a breakdown of the runtime spent in single-threaded regions, compared with OpenMP regions on Power and AArch64 platforms.
  • [FOR-6913] Python profiling now supports Python libraries with build type suffixes, for example libpython3.5mu.so.
  • [FOR-6886] Fixed an issue that occurs when using the PGI compiler to link with the static MAP sampler library.

19.0.5

  • [FOR-7210] Fixes an issue where Forge could not be launched on some alternative window managers like Fluxbox.
  • [FOR-6988] Fixes an issue when debugging static PGI binaries.
  • [FOR-7106] Fixes an issue where the number of OpenMP threads were not being set correctly when using express launch.
  • [FOR-7094] Fixes an issue where processes launched by srun would have their CPU affinity settings reset.

Known issues

Please refer to the known issues page.

Release Note for Release History 19.0 - latest update 19.0.5

Changes in this release

Arm Forge 19.0 covers the following releases:

  • Arm Forge 19.0.0 - Released 7th December 2018
  • Arm Forge 19.0.1 - Released 18th December 2018
  • Arm Forge 19.0.2 - Released 25th January 2019
  • Arm Forge 19.0.3 - Released 1st March 2019
  • Arm Forge 19.0.4 - Released 29th March 2019
  • Arm Forge 19.0.5 - Released 3rd May 2019

Arm DDT new features and enhancements:

19.0.0

  • Syntax highlighting for Python is now supported.
  • GDB 8.1 is now available as a choice of debugger.

19.0.1

  • None in this release.

19.0.2

  • Improved recommendations for static linking in the Arm Forge user guide.

19.0.3

  • Items in the variables views can now be sorted by name. Click the title to sort items in the view.

19.0.4

  • None in this release.

19.0.5

  • None in this release.

Arm DDT bug fixes:

19.0.0

  • [FOR-6278] Pretty printer now shows content of a std::shared_ptr in the variable view.
  • [FOR-6257] Fixed an issue where strings containing "..." caused the GUI to crash.
  • [FOR-5802] Fixed an issue where memory alignment was ignored when memory debugging with guard pages was enabled.
  • [FOR-5712] Fixed an issue where unions were falsely classified as an array and could not be inspected.
  • [FOR-5412] You can now launch serial programs that are in the environment's path without specifying the full path.

19.0.1

  • [FOR-6407] Fixed a startup issue with CRAY ALPS.

19.0.2

  • [FOR-6117] Fixed an issue that caused formatting in the variable views to be hidden when selecting elements.
  • [FOR-6527] Fixed an issue in the previous release related to Qt5 pretty printers.
  • [FOR-6601] Fixed the display of complex Fortran structures in the variables views.

19.0.3

  • [FOR-6564] The Known Issues section of the Forge user guide has been updated to describe compilation flags for OpenMPI 3.x with GCC, to fix a startup issue.

19.0.4

  • [FOR-6741] Fixed an issue that prevents the display of process IDs in offline debug logs.
  • [FOR-6703] Fixed an issue that causes a memory debugging deadlock when collecting stack backtraces for memory allocations.

19.0.5

  • [FOR-7131] Fixes an issue which caused sparklines to be rendered incorrectly in DDT offline reports gathered on PowerPC platforms.
  • [FOR-7210] Fixes an issue where Forge could not be launched on some alternative window managers like Fluxbox.
  • [FOR-6988] Fixes an issue when debugging static PGI binaries.
  • [FOR-7106] Fixes an issue where the number of OpenMP threads were not being set correctly when using express launch.
  • [FOR-7094] Fixes an issue where processes launched by srun would have their CPU affinity settings reset.

Arm MAP new features and enhancements:

19.0.0

  • You can now profile Python scripts with Arm MAP. Refer to the 'Python Profiling' chapter in the Arm Forge user guide for further information.
  • Syntax highlighting for Python is now supported.
  • The following limitation that was required in releases prior to 18.0 has been removed from the Forge user guide: "Unwind information is not always compiled in by default on this platform. This may result in partial trace nodes being displayed in the MAP parallel stack view. To avoid this, programs that are not compiled with debug information (-g) should at least be compiled with the -fasynchronous-unwind-tables flag or the -funwind-tables flag, preferably the former."

19.0.1

  • None in this release.

19.0.2

  • None in this release.

19.0.3

  • None in this release.

19.0.4

  • Support for profiling debug versions of Python.

19.0.5

  • None in this release.

Arm MAP bug fixes:

19.0.0

  • [FOR-6217] Fixed an issue that caused a slowdown in MAP's analysis phase.
  • [FOR-5412] You can now launch serial programs that are in the environment's path without specifying the full path.

19.0.1

  • [FOR-6407] Fixed a startup issue with CRAY ALPS.

19.0.2

  • [FOR-6394] Fixed an issue on AArch64 builds, where multiple 'CPU Instructions' metric presets are visible from the Metrics menu.
  • [FOR-6510] Arm MAP can now profile applications when SHELL is unset.

19.0.3

  • [FOR-6564] The Known Issues section of the Forge user guide has been updated to describe compilation flags for OpenMPI 3.x with GCC, to fix a startup issue.

19.0.4

  • [FOR-6722] Fixed an issue that causes extra items to be shown in the Functions view.
  • [FOR-6791] Fixed an issue that causes the incorrect number of physical cores to be reported.
  • [FOR-6825] MAP can now display a breakdown of the runtime spent in single-threaded regions, compared with OpenMP regions on Power and AArch64 platforms.
  • [FOR-6913] Python profiling now supports Python libraries with build type suffixes, for example libpython3.5mu.so.
  • [FOR-6886] Fixed an issue that occurs when using the PGI compiler to link with the static MAP sampler library.

19.0.5

  • [FOR-7210] Fixes an issue where Forge could not be launched on some alternative window managers like Fluxbox.
  • [FOR-6988] Fixes an issue when debugging static PGI binaries.
  • [FOR-7106] Fixes an issue where the number of OpenMP threads were not being set correctly when using express launch.
  • [FOR-7094] Fixes an issue where processes launched by srun would have their CPU affinity settings reset.

Known issues

Please refer to the known issues page.

System requirements

Please refer to the supported platforms pages for Arm DDT and Arm MAP

Installation instructions

Run the graphical "installer" or the text-only "textinstall.sh" from the download tarball. You may choose to install just for you or for all users on your system.

If you are installing on a cluster, please make sure that it is available at the same path on every machine.

If you have a job submission system such as PBS or LoadLeveler running, please refer to the Configuration section in the Arm Forge user guide for additional setup information.

Full installation instructions are available in the Arm Forge user guide.

If you're installing the Remote Client for Windows, follow the instructions here.

Uninstalling Arm Forge

To uninstall Arm Forge, remove the installation directory from your system:

rm -r <installation-dir>

Licences

If you do not have licence files for each product you will need to obtain them from Arm - Get an evaluation license.

Full licences may be obtained by emailing HPCToolsSales@arm.com. Licence files should be stored in a directory called licences below the installation directory. For a default (root) installation, that directory would be:

/opt/arm/forge/licences

For a user-only installation it would be:

${HOME}/arm/forge/licences

Running DDT

If you are using a supported desktop environment (KDE or Gnome) you will find a DDT icon in your Development/Programming menu.

To run DDT from the command line, type:

{arm-forge-path}/bin/ddt

or, if {arm-forge-path}/bin is in your $PATH, just type:

ddt

You may optionally provide a program name as the first argument.

Upon startup you will be presented with the Welcome page. From here you may choose to run a program, attach to an existing program or open a core file.

To start debugging a program, choose "Run". In the Run window, set the path to your program in the Application field and click "Run" to start the program.

Your chosen program will be run using mpirun. If you have problems starting your program under DDT, first ensure it can run without DDT from the command line.

Running MAP

If you are using a supported desktop environment (KDE or Gnome) you will find a MAP icon in your Development/Programming menu.

To run MAP from the command line, type:

{arm-forge-path}/bin/map

or, if {arm-forge-path}/bin is in your $PATH, just type:

map

You may optionally provide a program name as the first argument.

Upon startup you will be presented with the Welcome page. From here you may profile a program, or load a profile from a previous run.

To start profiling a program, choose "Profile". In the Run window, set the path to your program in the Application field and click "Run" to start the program.

Your chosen program will be run using mpirun. If you have problems starting your program under MAP, first ensure it can run without MAP from the command line.

Examples

Example code can be found in the installation directory:

<INSTALL_DIR>/examples

Copy the example code to a writeable directory and run the examples using the makefiles provided.

Documentation

Once installed these release notes can be found in the installation directory, and on the Release History page on the Arm Developer website.

The Arm Forge user guide is available in the <INSTALL_DIR>/doc directory, or online here.
 
Further documentation, help and tutorials can be found on the Arm Developer website.

Support

If you require support or would like to provide feedback, please contact allinea-support@arm.com or use our support request form.