Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29281 Discussions

Stack vs. Save attribute and performance

ahasan
Beginner
‎03-19-2006 01:56 PM
690 Views
If a subroutine or functions is called repeatedly, such as the MainWindowProc() in a win32 program, is it better to use the SAVE attribute for all variables in that function or subroutine rather than using the stack?
I am curious about how this affects program performance or efficiency.
0 Kudos

Link Copied

2 Replies
Steven_L_Intel1
Employee
‎03-19-2006 05:50 PM
690 Views
Using SAVE will defeat some optimizations. Such routines don't tend to have large local variables, so the performance difference relative to the allocation type is probably not measurable. Stack is friendlier to cache than static.
0 Kudos
Copy link
ahasan
Beginner
‎03-19-2006 11:00 PM
690 Views
Thanks Steve. I appreciate the reply and info.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.