This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Debugging data on Alpha
- To: Jeffrey A Law <law at redhat dot com>, Bernd Schmidt <bernds at redhat dot com>
- Subject: Re: Debugging data on Alpha
- From: Daniel Berlin <dan at dberlin dot org>
- Date: Fri, 29 Dec 2000 22:54:00 -0500
- CC: Richard Henderson <rth at redhat dot com>, Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, Untitled <gcc at gcc dot gnu dot org>
On 12/29/00 11:47 AM, "Jeffrey A Law" <law@redhat.com> wrote:
> In message <Pine.LNX.4.30.0012291222320.24133-100000@host140.cambridge.redhat
> .com>you write:
>> I had an idea yesterday. I was working on a few patches that make us
>> keep the original pseudo register number in the second field of a REG,
>> so that we can look it up after reload has completed. The idea is that
>> maybe this could be used as a starting point for better debugging
>> support with register renaming and LRS optimizations. We'd stop bothering
>> with the BLOCK notes and re-create the necessary information during the
>> final pass by establishing a mapping between hard regs and user variables
>> at all points in the function.
>> I'm not really familiar with the debugging output code, so I can't tell
>> whether this is feasible. Comments?
> Hmmm. Interesting. The trick for debugging register renaming and LRS is
> that you have to be able to map a pseudo to a set of hard registers over
> specific lifetimes.
>
Wait, what's the problem again representing this in dwarf2? (Isn't this why
location lists exist?)
Or is it a stabs-only problem?