Warning Messages: WI*

• List of Warning Messages, Part1: WB*

• List of Warning Messages, Part2: WC*

• List of Warning Messages, Part3: WI*

• List of Warning Messages, Part4: WL*

WIa10

The FOR loop may be endless as the loop variable <%1> is limited. Thus the running condition is possibly always true.

WIa12

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

WIa13

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

WIa14

overflow detection for interval (%1) with specification (<%2> and <%3>) at element "%4"

WIa15

Interval (implementation) out of bounds in assignment to <%1> %2 := %3 (will NOT be limited)

WIa16

Increment/decrement operation on <%1> without limitation

WIa17

Interval out of bounds in assignment to <%1> %2 := %3 (will NOT be limited)

WIa181

Interval (float) out of bounds in assignment to <%1> %2 := %3 (will NOT be limited)

WIa182

Interval (float) out of bounds in initialization of variable <%1> %2 := %3 (will NOT be limited)

WIa183

Interval (float) out of bounds in implCast <%1> %2 := %3 (will NOT be limited)

WIa184

Interval (float) out of bounds in method argument to <%1> %2 := %3 (will NOT be limited)

WIa2

Index Interval %2 out of range %1 (will be limited)

WIa3

Arithmetic operation exceeds available bit length and may not be correct

WIa32

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

WIa33

Negation of an unsigned two's complement value should be avoided

WIa4

An additional numerical error is introduced by incompatible quantizations

WIa5

Type mismatch in call to service routine

WIa6

Non-linear formula <%1> of <%2> is treated as identity; code may be unexpected.

WIa61

Discrete element <%2> with non-identity formula <%1> – will be generated as cont type

WIa62

Element "%1" using %2 must have identity formula --- formula "ident" is used instead of formula "%3"

WIa63

Implementation flag "Limit to maximum bit length" is not supported for type %1

WIa66

Assignment of %1 reference from <%3> to <%2> with different implementations

WIa67

Assignment of <%2> to INOUT parameter <%1> with different implementations

WIa7

Implementation mismatch of variable <%1> and method argument <%2>

WIa8

Could not avoid division (scaling factor almost zero)

WIa9

Physical interval %1 of divisor contains zero.

WIa91

Loosing precision: interval chosen for denominator (%1) will lead to poor result due to values close to zero

WIa92

Loosing precision: interval chosen for denominator (%1) will lead to poor result due to values close to zero – use %2 instead

WIa93

Scaling %1 is not representable, using approximation %2 instead.

WIle1

binary operation exceeds available bit length and may not be correct

WIle11

arithmetic operation exceeds available bit length and may not be correct

WIle110

Two's complement operation with %1 bits wraps around, but the result is used with %2 bits

WIle111

Division with a constant followed by a multiplication with a constant is not reduced

WIle112

Conversion of expression of type %1 to %2 with overflow

WIle113

Conversion of a calculation from %1 to %2

WIle114

Implementation flag "Limit to maximum bit length" is not supported for type %1

WIle115

Conversion of a calculation with wrap-around to floating point

WIle12

arithmetic operation has singleton interval and may not be correct

WIle120

result of arithmetic operation is always %1 and may be incorrect

WIle121

result of arithmetic operation is always %1 or %2 and may be incorrect

WIle122

result of division has only two distinct values and may be inaccurate

WIle13

arithmetic division/shift right operation with large constant may lead to incorrect result

WIle130

taking the remainder of a negative value is compiler implementation defined

WIle14

potential overflow of 1 in integer division result for min_signed/-1, will be ignored

WIle15

potential division by 0, will be ignored

WIle150

Protection of %1 is not generated based on interval information of elements without assignment limitation

WIle151

Limitation of %1 is not generated based on interval information of elements without assignment limitation

WIle16

Arithmetic operation overflows by %1 bits, but only %2 bits are available

WIle17

Unable to limit expression correctly, since interval %1 has width of less than 1

WIle18

Approximation of <%1> by <%2> leads to an relative error of <%3> (which is bigger than <%4> given in the tool options)

WIle20

optional arithmetic service <%1> not found, will use alternative code

WIle201

found complement service definition for type "%1" in file "%2" without explicit redundant data type; using "%3" as redundant data type instead (Use "complement|%1|%3" to explicit define the redundant data type)

WIle21

Unknown service definition key "%1" in file "%2"

WIle22

Distribution is filled with identical axis points

WIle30

codegen.ini option entry >resolveSystemConstants=%1< not valid for experimental code – use default: %2

WIle31

codegen.ini option entry >resolveSystemConstants=%1< not valid – use default: %2

WIle35

codegen.ini option entry >%1< unknown --- ignored

WIle365896

Udisc/Sdisc may be generated in an unexpected way.

WIle40

unknown memory class %1 --- please provide specification in memory class declaration file "memorySections.xml"

WIle41

memory class not defined for reference <%1>

WIle42

different storage qualifier for memory class "%1" (used for '%2' reference stuct on stack) and "%3" (specified for array "%4")

WIle50

unreachable code after %1 statement --- removed

WIle51

Explicit %1 access to message "%2" ignored due to message usage variant option set to "%3"

WIle52

Read and write access to IRV <%1> differ – this maybe a modeling error

WIle53

Read and write access to IRV <%1> may differ – this maybe a modeling error OR complex conditions, which ASCET is not able to recognize as equal

WIle533

%1 access to %2 expected, but not found in runnable "%3"

WIle534

%1 call to operation "%2" expected, but not found in runnable "%3"

WIle5351

Access conditions for "%1" differ: Arxml "%2" vs Model "%3"

WIle5352

Access conditions for "%1" differ: Arxml missing, assuming "true" vs Model "%2"

WIle5353

ARXML info usage condition "%1" references unknown system constants: %2

WIle5354

Access conditions for port "%1" and access mode "%2" differ: Arxml "%3" vs Model "%4"

WIle5355

Access conditions for port "%1" and access mode "%2" differ: Arxml missing, assuming "true" vs Model "%3"

WIle54

Unable to perform read/write analysis for IRV <%1.*> – there are multiple instance of the record type within the project context

WIle56

Bad resolution for calculated Dt value ("%1") from period ("%2") using formula "%3" – please change formula for Dt

WIle560

Formula "%1" of category %2 must be transformed despite the "Keep specification" setting in order to meet the AUTOSAR requirements

WIle57

Calibration access of "%1" has been set to "%2" in order to synchronize all elements of memory class "%3"

WIle58

Rte_IStatus for implicit communication to element "%1" is not supported by selected RTE – missing support for "%2

WIle59

Rte_IStatus for implicit communication to element "%1" is not generated due to missing pre conditions. "RTE_E_OK" used instead

WIle60

The software component uses enumeration "%1". Check the ranges of the texttable compu-methods in the ARXML files generated by ASCET

WIle623

Possibly wrong avoiding of 0 for two-sided reciprocals

WIle76

Interval of assert operator %1 and operand interval %2 have no common values

WIle762841

Possible wrong optimization of comparison operation in former ASCETversions

WIle77

index <%1> possibly out of bounds for indexed expression "%2"%3

WIle78

index <%1> possibly out of bounds for indexed expression "%2", but unable to limit correctly.

WIle8

invalid compile time constant expression – floating point constant detected – generating runtime code instead

WIle81

Diagnostic code "%1" not activated – Group %2 not supported in ECU-SW

WIle92

Code will violate MISRA rule 10.1: cannot assign expression with interval %1 to type %2