TASKING VX-toolset for GTM v3.3r1 patch 1
Release Note

Scope

This release note covers the changes between v3.3r1 and v3.3r1 patch 1 of the TASKING VX-toolset for GTM.

For release notes prior to v3.3r1, please visit the TASKING GTM support website.

Contents

• Important Notices
• Build Numbers
• Fixed Issues in v3.3r1p1
• New Intrinsics
• Uninstalling the Patch
• License Information

Important Notices

This patch contains changes to the following components:

• GTM C compiler

Due to the fixed compiler issues, code size metrics may improve to a greater or lesser degree.

Please note that the GTM libraries have been rebuilt. These libraries are also part of this patch.

Build Numbers

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

• cmcs\bin\cmcs.exe

All other executable files still have the original v3.3r1 build number: Build 19071160

Fixed Issues in v3.3r1p1

Fixed Problems

• MCSVX-882 - Compiler does not use extended register set in obvious use case
• MCSVX-884 - MSB (bits 31-24) not cleared in memory after storing a 24-bit value (see New Intrinsics)
• MCSVX-887 - Superfluous stack usage in a use case not using -t4 size optimization

New Intrinsics

__store_u32 - Store unsigned value to memory with high byte initialization

void __store_u32( volatile unsigned int * addr, unsigned int val );

Write an unsigned integer value to memory with high byte initialization. Builtin store operator leaves the most significant byte contents undefined because a 24-bit source value is stored into a 32-bit memory location. This intrinsic zero extends the value by writing 0 to the MHB register before doing the store.

__store_s32 - Store signed value to memory with high byte initialization

void __store_s32( volatile int * addr, int val );

Write a signed integer value to memory with high byte initialization. Builtin store operator leaves the most significant byte contents undefined because a 24-bit source value is stored into a 32-bit memory location. This intrinsic sign extends the value by propagating its sign to the MHB register before doing the store.

Uninstalling the Patch

After installation of this patch, the directory backup_patch1 is present in the installation directory of the product.

1. Copy the contents of directory backup_patch1 to the installation directory. This way you overwrite the files installed by the patch.
2. Remove directory backup_patch1.

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 Altium or one of its distributors, a license key will be sent to you by email or on paper.

See Obtaining a License on our website for more information.

Local TASKING License Server (not applicable to evaluation licenses)

If you have ordered a TASKING product with a floating license, you can have it serviced by the Remote TASKING License Server (the most convenient solution) or through a Local TASKING License Server (in case you have no external network access for example). Consult your Altium representative for assistance on deciding what the best setup would be for your situation.

If you like to setup up a local license server, we kindly refer you for more information to Support for TASKING License Management System (TLM) on our website. Here you can also download the Local TASKING License Server package.

It is advised that you install the Local TASKING License Server before you install products that require this server.