This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Memory map.
- To: "Joern Rennecke" <amylaar at cygnus dot co dot uk>
- Subject: RE: Memory map.
- From: "Virgil Palanciuc" <Virgil dot Palanciuc at cs dot pub dot ro>
- Date: Wed, 24 May 2000 11:26:36 +0300
- Cc: "Gcc at Gcc dot Gnu. Org" <gcc at gcc dot gnu dot org>
> Variables that are volatile or have volatile fields are put straight into
> the stack; reload had nothing to do with them. Likewise, if a variable
> must be put into the stack because the address has been taken in a way
> that can't be optimized away, or due to a setjmp, the variable is put
> early into the stack - no later then when purge_addressof is called.
> Look for / at the macros TREE_THIS_VOLATILE, TYPE_QUAL_VOLATILE and
> the functions mark_addressable, put_var_into_stack, put_reg_into_stack.
I ran into a problem I didn't think of so far. What do I do if I have an
array declared in a function? I know no way of detecting this.
Can't I just use getdecls() to get all the info I need?
Virgil?