Visible to Intel only — GUID: GUID-89BDC7B8-B4B4-4BDF-A28F-57111ED8A516
Visible to Intel only — GUID: GUID-89BDC7B8-B4B4-4BDF-A28F-57111ED8A516
save-temps, Qsave-temps
Tells the compiler to save intermediate files created during compilation.
Linux: |
-save-temps -no-save-temps |
macOS: |
-save-temps -no-save-temps |
Windows: |
/Qsave-temps /Qsave-temps- |
None
Linux and macOS systems: -no-save-temps |
On Linux and macOS systems, the compiler deletes intermediate files after compilation is completed. On Windows systems, the compiler saves only intermediate object files after compilation is completed. |
This option tells the compiler to save intermediate files created during compilation. The names of the files saved are based on the name of the source file; the files are saved in the current working directory.
If option [Q]save-temps (C++) or is specified, the following occurs:
The object .o file (Linux and macOS) is saved.
The .obj file (Windows) object .o file is saved.
The assembler .s file (Linux and macOS) or .asm file (Windows) is saved if you specified the [Q]use-asm option.
The .i or .i90 file is saved if the fpp preprocessor is invoked.
If -no-save-temps is specified on Linux or macOS systems, the following occurs:
The .o file is put into /tmp and deleted after calling ld.
The preprocessed file is not saved after it has been used by the compiler.
If /Qsave-temps- is specified on Windows systems, the following occurs:
The .obj file is not saved after the linker step.
The preprocessed file is not saved after it has been used by the compiler.
This option only saves intermediate files that are normally created during compilation.
None
Example
If you compile program my_foo.F on a Linux or macOS system and you specify option -save-temps and option -use-asm, the compilation will produce files my_foo.o, my_foo.s, and my_foo.i.
If you compile program my_foo.fpp on a Windows system and you specify option /Qsave-temps and option /Quse-asm, the compilation will produce files my_foo.obj, my_foo.asm, and my_foo.i.