TASKING VX-toolset for TriCore v6.2r2 patch 2
This release note covers the changes between v6.2r2 and v6.2r2 patch 2 of the TASKING VX-toolset for TriCore.
For release notes prior to v6.2r2, please visit the TASKING
TriCore support website.
This patch contains changes to the following components:
TriCore C++ compiler
TriCore C compiler
TriCore control program (for C++ compiler invocations)
The stdbool.h header file (when used in C++ code)
TriCore libc++ header files
TriCore STLport C++ header files
SFR files for AURIX 2G
Please note that the TriCore libraries have been rebuilt.
These libraries are also part of this patch.
- C compiler error F103: out of memory
- Assembler astc: truncates command line option listing in generated object file
- Compiler reorders memory accesses to potentially aliasing locations
- Compound literals generate incorrect code in recursive functions
- Perennial C P64072 fails on overlapping struct initialization
- C compiler error ctc S900: internal consistency check failed
- C++ example using unordered map container does not build
- Incorrect conversion of an if-else statement to an expression
- Support EABI v3.0 compliant structure alignment in the C++ compiler (--eabi=W)
- C++ compiler warning W2639 when pragma section is used within extern "C"
- STLport C++ header files contain unnecessarily complex references to TASKING STL header files
- C++ compiler error when using stdbool.h
- C++ compiler does not allow section renaming for class static variables
- C++ compiler option --eabi=H assumes a minimum alignment of 4 for a struct/union larger than 1 byte
- C++ compiler alignment of "long long" with --eabi=H is 8 instead of 4
- Support EABI v3.0 compliant character bitfields in the C++ compiler (--eabi=C)
- SFR files allow unaligned access to GTM registers for TC3xx
- C++ compiler using C++ 2003 standard cannot process _Pragma(...)
After installation of this patch, the directory
backup_patch2 is present
in the installation directory of the product.
- Copy the contents of directory
backup_patch2 to the installation directory.
This way you overwrite the files installed by the patch.
- Remove directory
TASKING products are protected with TASKING license management software.
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.