This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Extracting live registers
- From: Segher Boessenkool <segher at kernel dot crashing dot org>
- To: Paulo Matos <pmatos@linki.tools>
- Cc: gcc at gcc dot gnu dot org
- Date: Wed, 7 Nov 2018 16:19:23 -0600
- Subject: Re: Extracting live registers
- References: <92eede92-8945-acb9-0230-63c9a928188d@linki.tools> <20181106234001.GG5994@gate.crashing.org> <98189988-e84a-1e49-ca4b-971f977d22c3@linki.tools> <20181107192742.GJ5994@gate.crashing.org> <4739850b-9d8f-c312-e1dd-a71bd259caa1@linki.tools>
On Wed, Nov 07, 2018 at 09:49:02PM +0100, Paulo Matos wrote:
> On 07/11/2018 20:27, Segher Boessenkool wrote:
> > Sure, it shows the register information at the edges of basic blocks
> > only. This is what you asked for btw ;-)
>
> True, but I need a way to map that information to the assembly
> instructions in the basic block. :)
With -dp you have the insn uids in the .s file, so you can match them up
with the RTL dumps. You can use -dP as well if you like that better.
> I think it's not impossible with all
> that gcc provides, but there's certainly a fair amount of parsing of
> these files, which is not ideal given their format might change under my
> feet.
Yes, the dump files are not meant for this. They aren't completely
parsable even.
Segher