Developer Guide and Reference

Contents

qopt-assume-safe-padding, Qopt-assume-safe-padding

Determines whether the compiler assumes that variables and dynamically allocated memory are padded past the end of the object.
Architecture Restrictions
Only available on all architectures that support Intel® Advanced Vector Extensions 512 (Intel® AVX-512) Foundation instructions

Syntax

Linux and macOS:
-qopt-assume-safe-padding
-qno-opt-assume-safe-padding
Windows:
/Qopt-assume-safe-padding
/Qopt-assume-safe-padding-
Arguments
None
Default
-qno-opt-assume-safe-padding
or
/Qopt-assume-safe-padding-
The compiler will not assume that variables and dynamically allocated memory are padded past the end of the object. It will adhere to the sizes specified in your program.
Description
This option determines whether the compiler assumes that variables and dynamically allocated memory are padded past the end of the object.
When you specify option
[q or Q]opt-assume-safe-padding
, the compiler assumes that variables and dynamically allocated memory are padded. This means that code can access up to 64 bytes beyond what is specified in your program.
The compiler does not add any padding for static and automatic objects when this option is used, but it assumes that code can access up to 64 bytes beyond the end of the object, wherever the object appears in the program. To satisfy this assumption, you must increase the size of static and automatic objects in your program when you use this option.
This option may improve performance of memory operations.