This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: does "assign_stack_local" from "function.h" automatically Do The Right Thing with debug information? [relates to the RTL-level if-conversion improvement project]
- From: Abe <abe_skolnik at yahoo dot com>
- To: Jeff Law <law at redhat dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Kyrill Tkachov <kyrylo dot tkachov at arm dot com>
- Date: Wed, 23 Sep 2015 18:35:34 -0500
- Subject: Re: does "assign_stack_local" from "function.h" automatically Do The Right Thing with debug information? [relates to the RTL-level if-conversion improvement project]
- Authentication-results: sourceware.org; auth=none
- References: <560311FF dot 2070303 at yahoo dot com> <560315BC dot 9020004 at redhat dot com>
On 09/23/2015 02:56 PM, Abe wrote:
I wonder if "assign_stack_local" from "function.h" automatically Does
The Right Thing with debug information?
Especially, does it cause the debug information, if any, for stack-frame
size to be updated accordingly?
If not, then would switching to "assign_stack_temp" be very likely to
solve the problem?
On 9/23/15 4:12 PM, Jeff Law wrote:
Neither inherently affects debug information. So if one is working and the other not, there's a deeper problem elsewhere.
Thanks.
No, I didn`t try with "assign_stack_temp". I was just wondering if that was likely to help, since I had what looked like a valid alternative.
Regards,
Abe