use of cpu registers under absoft

[ColinC]

Does anybody know how absoft handles the following:
In C one can 'hint' that the compiler ought to consider storing a value in a register only - not in RAM nor stack.
If a do loop index is used 'once only' within the loop, it is stored only in a register (or at least it was in the old days and ought to be).

To give a 'hint' to the absoft compiler, is it better to
(a) declare a temp variable and only use it over a few lines, and whenever one needs another temp variable to
declare another temporary variable, temp2;
or
(b) just using the same variable, temp, for all uses, will be okay.

Or does the Absoft compiler ignore such 'opportunities' to save RAM/cache and time?
Thanks for any ideas.
Colin

[mecej4]

How temporaries are handled is up to the compiler and may vary with the options given to the compiler.

When floating point quantities are involved in mixed mode expressions, older X86 CPUs had to store integer values into memory and load the memory contents into the FPU stack.

You can produce an .obj file and look at the disassembly to see the code emitted by a specific compiler.

[Jeremy]

For Absoft Pro Fortran, option (b) is the best.  Absoft Pro Fortran's optimizers will automatically determine the best place for variables will stored.