TASKING TriCore v6.3r1 Inspector v1.0r1
Release Note
Scope
This release note covers the initial features of the TASKING TriCore v6.3r1 Inspector v1.0r1.
Contents
TriCore v6.3r1 Inspector v1.0r1 is based on the TASKING VX-toolset for TriCore v6.3r1.
Inspector operates identical to the VX-toolset (except for the issue detection) down to the Linker.
Generation of the final executable image by the Linker has been disabled.
Components of the VX-toolset dealing with the final executable image, library sources and examples have been removed from the product.
Components modified for the issue detection have been renamed with prefix insp_ (insp_cctc, insp_cptc, insp_ctc, insp_astc, insp_ltc).
By default, Inspector detects and reports the full set of supported issues. You can use the following options to customize this set:
--ignore=<issue-id>,... - disables detection of specified issues.
--detect=<issue-id>,... - disables detection of all issues and enables detection of specified issues only.
These options are supported by the Control Program, C/C++ Compiler, Assembler and Linker. The issue ID corresponds to the issue's identification on the TASKING Issues Portal.
Inspector indicates issue detection by producing a warning message in two possible ways:
1. Definite detection.
Reported when Inspector can guarantee by detector's construction that the processed code is affected by the triggered issue. Note that the affected code may still be removed from the final executable image by subsequent optimizations or by the linker - this requires manual verification.
Example: ctc W999: [7/12] [INSP] detected occurrence of issue TCVX-44043.
2. Potential detection.
Reported when the issue is triggered, but Inspector cannot guarantee that the processed code has been affected. Location and/or some additional information will be reported to facilitate manual verification.
Example: ltc W998: [2/51] [INSP] detected potential occurrence of issue TCVX-43994.
Some potential detectors produce a lot of false positives. To narrow the processing, assembly comparison mode is introduced.
--detect-asm=<issue-id> - with this option Inspector only detects a single specified issue.
After initial potential detection Inspector generates two instances of the assembly code - affected and not affected by the issue.
If the comparison of these generated assembly files produces any meaningful difference, Inspector reports it and indicates locations of the generated files for the further analysis.
Inspector supports separate logging of detection messages.
--insp-log=<file> - with this option all detection messages are duplicated into the specified file.
The log file is written in append mode and clearing it at the right moment is your responsibility.
The logging mechanism supports concurrent writing for the multi-threaded build, but file locking over network is unreliable, so it should not be used with a remotely located log file.
- TCVX-39025
- LSL: prevent an allocation of the user stack in the PCP memory
- TCVX-40469
- Linker allows cloned sections outside the available DSPR0 memory range
- TCVX-40928
- AURIX multi-core: hex file does not contain code for cloned functions in ROM
- TCVX-43546
- Linker does not insert alignment_protection sections when a group includes sections with a different alignment
- TCVX-43868
- Run-time error for double _Complex expression passing to a function
- TCVX-43893
- C compiler omits value assignment to pointer type function argument with forward store optimization enabled
- TCVX-43913
- Compile-time concatenation of character string literal with unicode string literal fails
- TCVX-43915
- Unroll small loops optimization leads to wrong code when speed tradeoff -t0 used
- TCVX-43916
- C compiler - Generic Assembly Code optimization leads to false array index location in loop
- TCVX-43928
- Incorrect reordering of volatile memory reads
- TCVX-43940
- Erroneous code for a 'for' loop
- TCVX-43980
- Linker may hang when the size of an output section is at least 2 MB
- TCVX-43994
- Linker ltc allows duplicate interrupt vectors to be located in vector table
- TCVX-43998
- Invalid constant propagation with tripple indirection
- TCVX-44008
- Include file may be skipped when same filename is included from different directories
- TCVX-44014
- Missing initialization for local variable in a specific test case
- TCVX-44043
- Incorrect conversion of _Complex type to _Bool
- TCVX-44050
- Linker inserts section in an ordered, contiguous, fill group
- TCVX-44077
- C compiler generates malloc call for variable length array
- TCVX-44082
- Intrinsics __extracthwN and __extractbbyteN may return wrong result
- TCVX-44102
- Loop invariant code optimization issue
- TCVX-44201
- Linker - clone .text .clone code sections missing in copytable when using --non-romable option
- TCVX-44218
- Large floating-point numbers become zero when converted to _Float16
- TCVX-44224
- Wrong result multiplying two INIFINITY values when using software floating-point library
- TCVX-44231
- Wrong sizeof result for atomic_flag type
- TCVX-44237
- Illegal double word access to SFR register range
- TCVX-44245
- C compiler: wrong code generation when using packed structures with members of 16-bit signed types
- TCVX-44255
- C compiler: wrong code generation when using packed structures with some members declared as bit fields
- TCVX-44257
- Compiler violates EABI due to 4 byte user stack frame generation
- TCVX-44270
- Wrong code generation when using packed structures with some members declared as bit fields of width 17..24
- TCVX-44278
- C++ compiler: generated code results in address 0x0000000 access causing bus trap
- TCVX-44289
- Zero-sized bit-field does not create padding before subsequent bit-field with --eabi=B
- TCVX-44309
- MISRA C 2012 rule 10.4 checker reports false positive and fails to detect a violation
- TCVX-44339
- Subnormal values may incorrectly compare equal to zero
- TCVX-44383
- For non-trapping floating point comparisons: NaN == NaN incorrectly returns true
- TCVX-44387
- Erroneous code in code compaction function leads to invalid function parameter
- TCVX-44393
- Compiler issues double word accesses for data located in MCS memory
- TCVX-44400
- Wrong value is loaded into a 48-bit struct if used as a member of a larger 64-bit struct
- TCVX-44407
- C compiler front-end may produce imprecise FP result (±1 bit difference)
- TCVX-44417
- Compiler generates wrong code for loops with 64-bit iterators
- TCVX-44419
- Linker does not insert alignment_protection section when copy_unit is greater than 1
- TCVX-44421
- Conversion of float to integer raises "Overflow" instead of "Invalid operation" exception
- TCVX-44423
- libfprt: subnormal values incorrectly compare equal to zero
- TCVX-44426
- FPU version of C library is not selected with control program option --fp-model=St
- TCVX-44437
- Incorrect code for branch target align optimization when tail merging optimization active
- TCVX-44441
- Incorrect use of a loop instruction
- TCVX-44443
- Intrinsics __getbyteN and __gethwN may return wrong result
- TCVX-44453
- Incorrect propagation of __pure__ function call result
- TCVX-44461
- No error on narrowing conversion from char to bool
- TCVX-44522
- The __dsync() intrinsic does not always work as a memory fence
- TCVX-44545
- Overlapping sections created when a reserved section is used with a memory fill entry
Available detectors for each tool are also listed if option --detect is used without an argument
- TCVX-44325
- User stack pointer 4-byte aligned when interrupt occurs between FCALL and FRET
This issue has been deemed impossible to detect in any meaningful way during compilation. User manual contains a detailed description of the situation when the issue might occur.
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 Getting Started with the TASKING Inspector for TriCore
guide for information on obtaining a license.
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 TASKING 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.