|Global versus Stack variables email@example.com (shrey) (2005-11-19)|
|Re: Global versus Stack variables firstname.lastname@example.org (email@example.com) (2005-11-21)|
|Re: Global versus Stack variables firstname.lastname@example.org (glen herrmannsfeldt) (2005-11-21)|
|Re: Global versus Stack variables email@example.com (2005-11-21)|
|Re: Global versus Stack variables firstname.lastname@example.org (2005-11-21)|
|Re: Global versus Stack variables email@example.com (Jatin Bhateja) (2005-11-26)|
|Re: Global versus Stack variables firstname.lastname@example.org (2005-11-26)|
|Re: Global versus Stack variables email@example.com (Dave Thompson) (2005-12-05)|
|Date:||21 Nov 2005 22:46:30 -0500|
|Organization:||Department of Computer Science, University of Copenhagen|
"shrey" <firstname.lastname@example.org> writes:
> I was wondering if ppl can give their opinion on the following
> question. What is the impact of a variable being a global or a local
> variable on optimizations. In other words, is it likelier to produce
> better code if a variable is local than global. The reason I ask this
> is I wonder if register allocation is harder if a variable is global
> instead of local. Are there other optimizations which get affected due
> to this consideration.
As John said, it depends on your language and your compiler. But in
C-like languages on modern CPU's (with modern compilers), local
variables tend to be register allocated (unless their address is
taken) where global variables are memory allocated. This means that
access to gobal variables usually require a memory reference, though a
function can sometimes make a temporary copy in a register and use
this for several accesses. It must write back before returning,
calling another function or accessing a variable that might be aliased
with the global variable.
Local variables sometimes also need to be stored across function
calls, though, but you can often reduce the need for this by expoiting
the caller-saves/callee-saves division of registers.
Return to the
Search the comp.compilers archives again.