This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Debugging info on # spills?
- From: Mostafa Hagog <MUSTAFA at il dot ibm dot com>
- To: Michael Matz <matz at suse dot de>
- Cc: Daniel Berlin <dberlin at dberlin dot org>, gcc at gcc dot gnu dot org, "Timothy J. Wood" <tjw at omnigroup dot com>, Vladimir Makarov <vmakarov at redhat dot com>
- Date: Fri, 9 Apr 2004 09:25:16 +0300
- Subject: Re: Debugging info on # spills?
Michael Matz <matz@suse.de> wrote on 08/04/2004 16:37:13:
> Hi,
>
> On Thu, 8 Apr 2004, Mostafa Hagog wrote:
>
> > How about a different but related question.
> > Is there a way to get the number of spilled registers in a given
> > compilation?
>
> Yes, it's simply all pseudos which didn't get a hardreg, i.e. for which
> reg_renumber[p] is < 0 and which are equivalent to nothing.
But even this is not dumped anywhere, right?
>
> But that doesn't say anything about the cost of the added spill code. In
> the new-ra branch I have some small dumper which basically counts the
cost
> of all stack related loads and stores. Under the premise that it is
> constant before register allocation it gives at least some relatively
sane
> number about the quality of allocation.
>
Is the new-ra branch stable enough to run SPEC?
>
> Ciao,
> Michael.