This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: [tree-ssa] copy prop vs. debugging
- From: Richard Henderson <rth at redhat dot com>
- To: Andrew MacLeod <amacleod at redhat dot com>
- Cc: Jeff Law <law at redhat dot com>, Jason Merrill <jason at redhat dot com>, Diego Novillo <dnovillo at redhat dot com>, gcc mailing list <gcc at gcc dot gnu dot org>
- Date: Wed, 9 Jul 2003 10:49:36 -0700
- Subject: Re: [tree-ssa] copy prop vs. debugging
- References: <200307031648.h63GmnJh007209@speedy.slc.redhat.com> <1057760521.29596.29.camel@p4>
> Debuugging might seem wrong if a user variable
> isn't actually used in the last half of the program, but the value
> changes all the time because we are reusing the stack slot... Or is that
> OK? It would complicate things a little bit to make sure that doesnt
> happen.
It's ok outside of -O0. We get that effect anyway from variables
in registers that get re-used after they're dead.
The Most Proper thing to do in this case is to make sure that the
dwarf2 location lists express the fact that the user variable is
live between points A and B, and not across the entire scope.
r~