TASKING VX-toolset for Arm v7.0r1
Release Note

Scope

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

For release notes prior to v7.0r1, please visit the TASKING Arm support website.

Contents

• Important Notices
• Build Numbers
• New in v7.0r1
• Fixed Issues in v7.0r1
• Quick start
• License Information

Important Notices

This is the first public release of TASKING VX-toolset for Arm which supports NXP S23Z and S32E series.

The product includes the following features:

• TASKING VX-toolset for Arm supports all NXP S32Z27x and S32E27x devices that are currently available.
• TASKING VX-toolset for Arm supports the iSYSTEM debugger.You can start the iSYSTEM debugger from the TASKING Eclipse environment.

  Note 1: The iSYSTEM debugger included in the product will be installed the first time you create a new debug configuration. You can also start the installation manually. From the Window->Preferences dialog, select iSYSTEM and click the Install button. This Install button changes into an Update button after installation is done. The Update button is enabled when a new version of the iSYSTEM debugger is available.

  Note 2: The iSYSTEM debugger is not supported under Linux.

• TASKING VX-toolset for Arm has the Safety & Cybersecurity Manual included in the product.
• TASKING VX-toolset for Arm is a 64-bit product. Only Windows 64-bit and Linux 64-bit hosts are supported.
• The Eclipse/CDT distribution version 2023-03 is shipped with the product.
• The Eclipse/CDT distribution includes a plugin containing the JustJ Java Runtime Environment. This JRE is used during the execution of the TASKING Eclipse environment.
• Discontinued support for the embedded ST-Link over USB debug adapter.

Build Numbers

All executable files in this release have the following build number: Build 23112967.

New in v7.0r1

• Support for Armv8-R AArch32 architecture profile.
• Support for Arm Cortex-R52.
• Support for NXP S23Z and S32E series.
• Eclipse integration with the iSYSTEM debugger (winIDEA). Currently, for Windows version only.
• The Eclipse Platform distribution version 4.27 is shipped with the product.
• The Eclipse distribution includes JustJ JRE version 17.0.6.
• The C compiler supports the ISO/IEC 9899:2018 (C17) language standard.
• The EDG C++ front-end is updated to version v6.3.
• The C++ library is updated to LLVM release v14.0.6.
• The following C++ compiler options are considered superfluous and are removed from the product:
  • --anachronisms
  • --auto-type
  • --c++11-sfinae
  See more...

  • --compound-literals
  • --delegating-constructors
  • --dollar
  • --lambdas
  • --namespaces
  • --no-auto-storage
  • --no-auto-type
  • --no-bool
  • --no-extern-inline
  • --no-namespaces
  • --no-nonconst-ref-anachronism
  • --no-nullptr
  • --no-rvalue-refs
  • --no-typename
  • --no-wchar_t-keyword
  • --nonconst-ref-anachronism
  • --nonstd-default-arg-deduction
  • --nonstd-instantiation-lookup
  • --nonstd-using-decl
  • --nullptr
  • --old-for-init
  • --old-line-commands
  • --old-specializations
  • --preserve-lvalues-with-same-type-casts
  • --rvalue-ctor-is-not-copy-ctor
  • --rvalue-refs
  • --uliterals
  • --unrestricted-unions
  • --user-defined-literals
  • --variadic-macros
  • --variadic-templates
  • --base-assign-op-is-default
  • --c++11-sfinae-ignore-access
  • --default-nocommon-tentative-definitions
  • --deprecated-string-conv
  • --friend-injection
  • --guiding-decls
  • --implicit-include
  • --incl-suffixes
  • --long-lifetime-temps
  • --multibyte-chars
  • --no-c++11-sfinae
  • --no-c++11-sfinae-ignore-access
  • --no-class-name-injection
  • --no-const-string-literals
  • --no-dep-name
  • --no-distinct-template-signatures
  • --no-explicit
  • --no-for-init-diff-warning
  • --no-variadic-macros
  • --nonstd-anonymous-unions
  Note: The default behavior is according to the C++ standard.

Fixed Issues in v7.0r1

Fixed Problems

• ARMVX-39577 C++ compiler: uppercase sub-options of -E/--preprocess do not work
• ARMVX-39578 C++ compiler option --no-stdinc does not work
• ARMVX-39631 Formatted output issue when precision specifier used with non null-terminated string
• ARMVX-39682 C compiler may incorrectly contract expressions
• ARMVX-39702 C++ compiler option --no-stdinc does not work
• ARMVX-39703 C++ compiler: uppercase sub-options of -E/--preprocess do not work
• ARMVX-39708 The __DMB() intrinsic does not always work as a memory fence
• ARMVX-39710 Evaluation of floating expressions involving NaN may produce wrong results
• ARMVX-39713 Overlapping sections created when a reserved section is used with a memory fill entry
• ARMVX-39714 C compiler: flexible array member initialization: diagnostics may be missing
• ARMVX-39717 Optimization ignores __weak__ attribute in the code
• ARMVX-39719 Wrong symbol value for empty copy table sub-table
• ARMVX-39721 Compiler ignores variable value change after this has been passed by reference in a function call
• ARMVX-39725 C compiler error S900 internal consistency check failed - please report
• ARMVX-39727 Linker feature --whole-archive ignores object modules without exported symbols
• ARMVX-39740 Wrong code generation for an if-else statement
• ARMVX-39742 ARM C++ compiler emits _Float16 variables as float in output
• ARMVX-39752 Compiler conducts a signed division instead of an unsigned one in a specific use case
• ARMVX-39753 C compiler ignores cast in a specific use case for a function return value
• ARMVX-39759 C compiler may leave empty .src file when it is killed
• ARMVX-39762 Header file setjmp.h - MISRA C check disabling not restored to default
• ARMVX-39768 Compiler generates wrong code for loops with 64-bit iterators
• ARMVX-39774 Flow optimization causes missing read operation
• ARMVX-39776 Wrong ABS pattern optimization for float or double
• ARMVX-39783 Loop invariant code optimization issue
• ARMVX-39784 Wrong iterator values after jumping into loop
• ARMVX-39786 Syntax to define an SVCall interrupt is not included in the user guide
• ARMVX-39790 Memory access out of bounds due to a missing conversion of the loop increment
• ARMVX-39791 Signed instead of unsigned division/modulo
• ARMVX-39793 Incorrect constant propagation
• ARMVX-39794 Forward store optimization for weak variable causes NULL pointer dereference

TLM Fixed Problems

• Clients configured to use joined licenses via the special license key "PRODUCT" cannot be borrowed. Please note, that the new license pool mechanism, as supported by the TASKING Local License Server v1.5r3, is the preferred way now to group multiple licenses instead of using "PRODUCT".
• Licborrow reports the requested number of days as granted even if this is limited by the license server
• Licborrow diagnostic message on the Check License button is not clear
• Uninstall should remove license environment variable

Quick Start

For a quick start, just start the 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.

License pool mechanism

You can now define a named pool of specific licenses on the local license server.

A license pool is useful to specify that the licenses for one or more products shall be grouped together. This can be the case for example when your license agreement has constraints on geographical location, such as a single site license, country license or continental license. In that case you can put all product licenses that are allowed to be used by a specific location into a license pool.

Pool names for TASKING products released after March 2023 have the syntax POOL-name, where the name is free to choose from 1 up to 14 characters. Pool names are also supported with existing TASKING products, as long as you use the TASKING Local License Server v1.5r3 or up and specify the pool names in the fixed format POOL-xxxx-xxxx-xxxx.
Note that you also need to use this fixed pool name format if you are mixing older and newer TASKING products.

The PRODUCT keyword has been deprecated, but still works for backwards compatibility.

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.