Information Messages

Temporary variable used at <%1>

Interval (physical) mismatch in assignment to <%1> %2 := %3 (will be limited)

Interval (implementation) mismatch to <%1> %2 := %3 (will be limited)

Assignment of floating point expression to integer variable with limitation

Increment/decrement operation on <%1> without limitation

Arithmetic (%1) operation overflows by %2 bits (will be handled by %3)

Expression with %1 bit type on the left hand side will be generated with %1 representable bits (project setting is %2 bits)

Expression containing a value with %1 bit type will be generated with %1 representable bits (project setting is %2 bits)

Non-linear formula <%1> of <%2> with master set to model may lead to unexpected code.

Component "%1" is generated with "Prototype Implementation" specified

Remainder is protected against rem-by-0

Division is protected against division-by-0

Division is protected against signed overflow

No approximation of %1, due to calculation in discrete context

Temporary variable %1 read and written with different system constant conditions

Interval of assert operator %1 is not contained in operand interval %2

Operand interval %2 is contained in interval of assert operator %1

Implementation cast %1 without assignment limitation can be replaced by an assert operator with interval %2

Diagnostic code group %1 has been activated

Ignored %1 access for element "%2" of type Module due to single instance semantics

Ignored pre/post hook specification "%1" for task "%2", since monitoring is disabled

Hint: select "%1" in project option "%2" for %3

%1 command requires message usage variant option to be set to %2 instead of %3 --- will be set for code generation

%1 - please %2

The initialization value of <%1> is unequal to zero. The variable will not be placed in cleared initialization section.

Memory class "%1" specified for %2 should be a const data section (%3)

%1 specification of <%2>: "%3" is "%4"

Deprecated feature: asReference flag is set for element <%1> in C code component. Declare an explicit reference instead!

constant folding – reduced %1 statement to THEN statement

constant folding – reduced %1 statement to ELSE statement

constant folding – reduced %1 statement to EMPTY statement

constant folding – reduced %1 statement to %2

constant folding – reduced %1 to EMPTY statement

reduced assignment without side effects to EMPTY statement

Sequencing should start with %1, but starts with %2

Sequencing should have step size %1, but have step size %2

Use %2 access semantics for element "%1" - as defined in imported ARXML

Variable <%1> never used within current project configuration – this analysis is done due to variant coded data structure generation

Executable <%1> never used within current project configuration – this analysis is done due to variant coded data structure generation

method argument "%1" with memory class "%2" is not a reference – reset memory class to "Default"

No conversion to intermediate representation for %1 mapping of message "%2" to ECU label "%3"

Operation with reciprocal value behaves differently than before ASCET V6.2

Init value of reciprocal element is generated differently than before ASCET V6.2

method local variable <%1> not used in <%2>

method argument <%1> not used in <%2>

method <%1> not used in this project

Variable name "%1" begins with an underscore may lead to name clashes in the generated code

Variable "%1" without implementation got the implementation <%2>

Variable "%1" has a specified implementation in the mixed physical generation

INOUT method argument <%1> has not been assigned at each return point

assignment to INOUT method argument <%1> before its value is read, argument can be set to OUT direction

state reset method has no specified body – no code is lost