TASKING VX-toolset for Arm v7.1r1p1
Release Note

Scope

This release note covers the changes between v7.1r1 and v7.1r1p1 of the TASKING VX-toolset for Arm.

For release notes prior to v7.1r1p1, please visit the TASKING Arm support website.

Contents

• Important Notices
• Build Numbers
• Fixed Issues in v7.1r1p1
• Quick start
• License Information

Important Notices

Device support

Added support for the following devices:

• GigaDevice: GD32A71x, GD32A72x and GD32A74x devices.
• TongXin: THA6206 and THA6412 devices.

To get winIDEA support for these devices, please update winIDEA from the Window->Preferences dialog, select TASKING winIDEA and click the Update button. The Update button is enabled when a new version of the winIDEA debugger is available. The winIDEA debugger is not supported under Linux.

It is also recommended to update the TASKING Eclipse plugin. For more information, see this knowledge base article.

Changed components

This patch contains changes to the following components:

• Arm ELF archiver (ararm)
• Arm C compiler (carm)
• Arm HLL object dumper (hldumparm)
• Arm object linker (lkarm)
• All libraries (*.ma, *.lib) have been rebuilt and are also part of this patch.

Enhanced linker map file options

Due to the fix of issue ARMVX-39893 "Long symbol and section names are spread across multiple lines within a map file", existing linker options --map-file=TEXT and --global-map-file=TEXT can be extended with ":0". This will disable the default wrapping of long lines or table cells. For example: --map-file=output.map:TEXT:0. The same applies to linker option: --global-map-file.

Build Numbers

For this patch, the following executable files have an updated build number: Build 25012365.

• carm\bin\ararm
• carm\bin\carm
• carm\bin\hldumparm
• carm\bin\lkarm

All other executable files still have the original v7.1r1 build number: Build 24082661.

Fixed Issues in v7.1r1p1

Fixed Problems

• ARMVX-39900 - Incorrect aliasing analysis of restrict pointer expression after PRE
• ARMVX-39898 - Zero size value for output section definitions in LSL file is not permitted
• ARMVX-39893 - Long symbol and section names are spread across multiple lines within a map file
• ARMVX-39891 - Missing MISRA C:2012 rule 9.1 violation error for conditional initialized automatic with -OP
• ARMVX-39890 - Incorrect forward store optimization
• ARMVX-39889 - Aliasing not detected for static variables
• ARMVX-39886 - Clustering optimization generates code with an incorrect relocation
• ARMVX-39884 - Compiler errors E276 and E333 using designated initializers with a non constant value
• ARMVX-39878 - Enabling C compiler warning level 2 might provoke S900 internal error
• ARMVX-39876 - Packed structure is initialized with normal store instead of __unaligned store
• ARMVX-39872 - Incorrect loop unrolling
• ARMVX-39855 - Missing diagnostic for some uses of the _Alignof operator
• ARMVX-39854 - Missing diagnostic for some cases with name redeclaration
• ARMVX-39853 - Constant expressions are more general than defined by the C standard
• ARMVX-39850 - Missing diagnostic for an empty include file name
• ARMVX-39749 - C compiler: VLA: error S911: internal consistency check failed - please report
• ARMVX-39712 - Linker error F006: read error: .\<library name> has no size
• ARMVX-39678 - Archiver option -w/--warning does nothing

Quick Start

For a quick start, just start the Arm Eclipse IDE from the Start menu. This will start the Eclipse based development environment. You will be asked to select a workspace. In case you used Eclipse before it is recommended to select a new workspace. After clicking OK, you will see the 'Welcome' view. On this view you will see icons that link to specific information.

License Information

TASKING products are protected with TASKING license management software.

License key

You need a license key when you install a TASKING product on a computer. When you order a TASKING product from TASKING or one of its distributors, a license key will be sent to you by email or on paper.

See the TASKING License Management (TLM) Support page for information on obtaining a license.

Improved Verbose Logging

You can set the TSK_LOG_VERBOSE option in licopt.txt, or as an environment variable, to different verbose levels.

With level 3 or higher, detailed license configuration information is shown, which is useful for debugging licensing problems. For example, it shows the environment variables or options used, the license key and the search path.

Support for wait for a free license

You can now set the TSK_LICENSE_WAIT option in licopt.txt to a configurable time period to wait for a free license seat to become available instead of directly terminating when a license request is denied.

Wait for Available Process

If your license specifies a maximum number of processes you are allowed to use, you can set the TSK_PROCESS_WAIT option in licopt.txt, or as an environment variable, to the parallel process time-out (default: unlimited). This specifies the number of seconds the system is allowed to wait for a process to run if the maximum number of parallel processes permitted by the license is already running.

Better Support for Comments

In all license files (licopt.txt, licdopt.txt, licfile.txt, licdfile.txt, licdaccess.txt) you can add comments, not only on a separate comment line, but also at the end of a line. Comments start with the # character.