Intel® Fortran Compiler 17.0 Developer Guide and Reference
Determines whether the compiler assumes that variables and dynamically allocated memory are padded past the end of the object. Option -qopt-assume-safe-padding is the replacement option for -opt-assume-safe-padding, which is deprecated.
Only available on Intel® 64 architecture targeting the Intel® Xeon Phi™ coprocessor x100 product family (formerly code name Knights Corner)
Linux: | -qopt-assume-safe-padding -qno-opt-assume-safe-padding |
macOS: | None |
Windows: | /Qopt-assume-safe-padding /Qopt-assume-safe-padding- |
None
-qno-opt-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. |
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.
None