Lines Matching full:applications
18 The layout of v-table has been changed. Call of any virtual method at higher position in this class or its subclasses may result in crash or incorrect behavior of applications.
39 1) Applications will not provide the implementation for this pure virtual method and therefore cause a crash in the library trying to call this method.
40 2) The layout of v-table has been changed. Call of any virtual method at higher position in this class or its subclasses may result in crash or incorrect behavior of applications.
58 The layout of v-table has been changed. This leaf class has no exported constructors and therefore applications will copy an old v-table of the class that will not contain a pointer to added virtual method. Call of any method in this class may result in crash or incorrect behavior of applications.
114 The layout of v-table has been changed. Call of this virtual method or any virtual method at higher position in this class or its subclasses may result in crash or incorrect behavior of applications.
132 The layout of v-table has been changed. Call of this virtual method or any virtual method at higher position in this class or its subclasses may result in crash or incorrect behavior of applications.
169 Applications will pass parameters of older replaced method to newly added virtual method. This may result in crash or incorrect behavior of applications.
187 Applications will provide an older method to the library instead of expected newely added virtual method. This may result in crash or incorrect behavior of applications.
205 Call of any method in this class may result in crash or incorrect behavior of applications.
223 The layout of v-table has been changed. Call of this virtual method may result in crash or incorrect behavior of applications.
241 The layout of v-table has been changed. Call of this pure virtual method implementation may result in crash or incorrect behavior of applications.
259 Method @new_value will be called instead of @old_value by old applications.
277 Method @new_value will be called instead of @old_value by old applications.
295 1) An object of this class can be allocated by the applications and old size will be hardcoded at the compile time. Call of any exported constructor will break the memory of neighboring objects on the stack or heap.
314 Previous accesses of applications to public fields of this class or its subclasses may be incorrect.
332 1) The class has only inline or auto-generated constructors which will be copied to applications at compile time and will allocate an older memory layout. Call of any exported method of this class may access a memory outside the allocated objects or inside the older memory structure and result in crash or incorrect behavior of applications.
351 Possible incorrect access of applications to the memory occupied by the base classes.
499 Possible incorrect access of applications to the memory occupied by the base classes.
611 Possible incorrect access of applications to the memory occupied by the base classes.
629 The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications.
647 The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications.
665 Layout of parameter's stack of several functions has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
683 Applications will access incorrect memory when attempting to access this field.
701 1) Applications will access incorrect memory when attempting to access this field.
739 NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications.
759 NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications.
777 Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
796 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
815 NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications.
833 Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
852 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
871 NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications.
889 NOTE: this field should be accessed only from the new library functions, otherwise it may result in crash or incorrect behavior of applications.
907 Applications will access incorrect memory when attempting to access this field.
925 1) Applications will access incorrect memory when attempting to access this field.
926 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
944 1) Applications will access incorrect memory when attempting to access this field.
963 1) Previous accesses of applications to the removed field will be incorrect.
964 2) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
1000 Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
1018 1) Layout of structure fields has been changed and therefore fields at higher positions of the structure definition may be incorrectly accessed by applications.
1037 1) Applications may access incorrect memory when attempting to access this field.
1056 Applications may access incorrect memory when attempting to access this field.
1110 Applications may execute a wrong branch of code in the library and therefore change the behavior.
1128 This may result in crash or incorrect behavior of applications because the library may not handle removed member anymore.
1146 Applications may execute a wrong branch of code in the library and therefore change the behavior.
1182 Applications may execute a wrong branch of code in the library and therefore change the behavior.
1218 This field may be incorrectly initialized or accessed by applications.
1236 Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken.
1254 1) This field may be incorrectly initialized or accessed by applications.
1274 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken.
1292 Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken.
1347 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken.
1365 Possible access of applications to incorrect memory through the pointer.
1401 applications.
1419 The library functions will treat the value of this field as the lower-dimension array and will not read all elements. This may change the behavior of applications.
1437 Previous accesses of applications and library functions to this field may be broken.
1455 Previous accesses of applications and library functions to this field may be broken.
1473 Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken.
1492 2) Previous accesses of applications and library functions to this field may be broken.
1511 2) Previous accesses of applications and library functions to this field and fields at higher positions of the structure definition may be broken.
1529 Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken.
1584 2) Previous accesses of applications and library functions to the fields at higher positions of the structure definition may be broken.
1620 The fields or parameters of such data type may be incorrectly initialized or accessed by old client applications.
1662 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
1680 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
1698 Applications will pass an old default (compile-time) argument that may not be properly handled anymore. This may result in crash or incorrect behavior of applications.
1716 Applications will pass an old default argument (that is not default any more) that may not be properly handled anymore. This may result in crash or incorrect behavior of applications.
1752 The parameter became passed in different register. Applications will read the wrong memory block instead of the parameter value. Also, distribution of other parameters on the available registers and stack may be changed.
1770 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
1788 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
1806 The parameter became passed in the register instead of the stack. This may result in crash or incorrect behavior of applications.
1824 The parameter became passed through the stack instead of the register. This may result in crash or incorrect behavior of applications.
1860 This function may change parameter @target, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications.
1878 This function may change parameter @target, but it will be treated as const by old client applications. This may result in crash or incorrect behavior of applications.
1896 Added a new restriction on the parameter: if the memory addressed by the restrict-qualified pointer is modified, no other pointer will access that same memory. The compiler may choose to optimize new library code involving restrict-qualified pointers in a way that might result in incorrect behavior of old applications, that don't meet this restriction.
1968 Violation of the calling convention. This may result in crash or incorrect behavior of applications.
1986 Violation of the calling convention. This may result in crash or incorrect behavior of applications.
2004 Applications will read the wrong memory block instead of the parameter value.
2022 Violation of the calling convention. This may result in crash or incorrect behavior of applications.
2040 The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications.
2058 The return value will be treated as non-const by old client applications. This may result in crash or incorrect behavior of applications.
2076 This parameter may be incorrectly initialized by applications.
2112 The library function may try to access unallocated memory by the dereferencing of old parameter value and therefore cause a crash of applications.
2130 The library function will treat the parameter as the lower-dimension array and will not read all elements. This may change the behavior of applications.
2131 NOTE: if this is out-parameter then this change may cause a crash of applications.
2149 Applications will obtain a different return value and execution may change.
2167 Applications will obtain a different value and execution may change.
2221 This global data may be incorrectly accessed by applications.
2239 Applications will obtain a different value and execution may change.
2257 Applications will not obtain a return value and execution may change.
2275 1) Applications will read the wrong memory block instead of the return value.
2276 2) Layout of parameter's stack has been shifted by @word_size bytes because the hidden first argument, that is used to pass the return value, has been removed. All the parameters will be incorrectly initialized by applications.
2294 1) Applications will read the wrong memory block instead of the return value.
2295 2) Distribution of parameters on the available registers and stack has been changed because the hidden first argument, that is used to pass the return value, has been removed. All the parameters will be incorrectly initialized by applications.
2313 Layout of parameter's stack has been shifted by @word_size bytes because the return value became passed in memory as the hidden first argument, that was used to pass the return value. All the parameters will be incorrectly initialized by applications.
2331 Distribution of parameters on the available registers and stack has been changed because the return value became passed in memory as the hidden first argument, that is used to pass the return value. All the parameters will be incorrectly initialized by applications.
2367 1) The return value became passed in memory as the hidden first argument (address of the space on the stack provided by the caller) instead of the register and therefore the layout of parameter's stack has been shifted by @word_size bytes. All the parameters will be incorrectly initialized by applications.
2368 2) Applications will read the wrong memory block instead of the return value.
2386 1) The return value became passed in different register as the hidden first argument (address of the space on the stack provided by the caller) and therefore distribution of parameters on the available registers and stack will be changed. All the parameters will be incorrectly initialized by applications.
2387 2) Applications will read the wrong memory block instead of the return value.
2405 1) The return value became passed in register instead of the hidden first argument (address of the space on the stack provided by the caller) and therefore the layout of parameter's stack has been shifted by @word_size bytes. All the parameters will be incorrectly initialized by applications.
2406 2) Applications will read the wrong memory block instead of the return value.
2424 1) The return value became passed in register instead of the hidden first argument, that is passed in different register, and therefore distribution of parameters on the available registers and stack will be changed. All the parameters will be incorrectly initialized by applications.
2425 2) Applications will read the wrong memory block instead of the return value.
2443 This data will be copied to applications at compile time. Any attempts to change this global data by library functions may result in crash of applications.
2461 This data will be treated as const by old client applications. Any attempts to change this global data by library functions may result in undefined behavior.
2479 Any attempts of old applications to change this global data may result in crash.
2497 Any attempts of old applications to change this global data may result in crash.
2515 Applications will obtain a different return value and execution may change.
2551 Applications will treat the return value as the lower-dimension array and will not read all elements. This may change the behavior of applications.
2569 Applications may try to access unallocated memory by the dereferencing of new return value and therefore cause a crash.
2659 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
2677 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
2695 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
2713 Layout of parameter's stack has been changed and therefore parameters at higher positions in the stack may be incorrectly initialized by applications.
2749 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2767 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2785 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2803 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2821 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2839 The name of the appropriate symbol for this data on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2857 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2875 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2893 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2911 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2929 The name of the appropriate symbol for this function on binary level has been changed from @old_value to @new_value. This may cause "undefined reference" linker error in old client applications.
2947 Applications will pass an old value of this constant as the parameter to the new-version library functions, that expect a new one. This may result in crash of incorrect behavior of applications.
3001 The value of this field can begin to change in ways outside the control of old client applications.
3037 Old client applications will get volatile object instead of non-volatile, but may be optimized by the compiler and cannot handle volatile objects.
3055 Old client applications will pass volatile object to the function that may be optimized by the compiler and cannot handle volatile objects.
3073 This field may be incorrectly initialized or accessed by applications.
3091 This field may be incorrectly initialized or accessed by applications.
3109 This parameter may be incorrectly initialized by applications.
3127 This parameter may be incorrectly initialized by applications.
3145 Applications will obtain a different return value and execution may change.
3163 The return value became passed in different register. Applications will read the wrong memory block instead of the return value. Also, distribution of parameters on the available registers and stack may be changed.
3181 This parameter may be incorrectly initialized by applications.
3253 Applications will use an old value of this data instead of the new one. This may cause incorrect behavior of applications.
3271 The value of this field can begin to change in ways outside the control of old client applications.
3289 The value of this field can still be changed by const methods of old client applications, but it's not expected by new-version library.
3307 Old applications will continue using this method, but it may require a different initialization of the environment and parameters.
3325 Old applications will continue using this method, but it may require a different initialization of the environment and parameters.
3361 Old applications will continue using this global data, but it may require a different initialization of the environment.
3379 Old applications will continue using this global data, but it may require a different initialization of the environment.
3415 The value of this field is expected to be **const** in new library version, but can be modified by old applications.
3451 The value of this field is expected to be **const** in new library version, but can be modified by old applications.
3487 Old applications will continue using this field, but it may require a different initialization of class object.
3505 Old applications will continue using this field, but it may require a different initialization of class object.
3523 Old applications will not provide implementation for this pure virtual method. This may result in crash or incorrect behavior of applications.
3559 The internal structure of this type is hidden in the new library version and may be different. This may result in crash or incorrect behavior of applications.
