Displaying 6 results from an estimated 6 matches for "asmprinterflag".
Did you mean:
asmprinterflags
2015 Oct 19
4
Is there a way to determine what CPU resource is used by which instruction?
...which instruction during scheduling. This is purely for
debugging purposes. Since I'm somewhat new to LLVM it is a bit difficult
for me to figure this out.
Initial idea was to insert comments in the generated assembly which would
tell me what what resource is used. MachineInstr has a uint8_t
AsmPrinterFlags, which I want to use to pass information from the scheduler
to AsmPrinter about which resource is used. I've asked on the IRC channel
how to do it but nobody seems to know. A scheduling debug log was also
mentioned (supposedly it should provide me with the same information) but I
don't kno...
2009 Sep 14
0
[LLVMdev] [PATCH] Spill Comments
...ote:
> Attached is a patch to print asm comments for spill information.
> We've discussed the mechanisms before but I wanted to run the
> patch by everyone before I start to commit pieces.
Some thoughts:
The general approach to enhancing CreateStackObject and adding
MachineInstr::AsmPrinterFlags seems fine to me!
The testcase should use filecheck to avoid running llc 4 times. Also,
it seems better to design a situation where you just have 16 live
variables instead of taking some random function for gcc (you're
implicitly depending on how ra is handling this code instead of...
2009 Sep 11
7
[LLVMdev] [PATCH] Spill Comments
Attached is a patch to print asm comments for spill information.
We've discussed the mechanisms before but I wanted to run the
patch by everyone before I start to commit pieces.
-Dave
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spillcomments.patch
Type: text/x-diff
Size: 58930 bytes
Desc: not available
URL:
2009 Sep 14
1
[LLVMdev] [PATCH] Spill Comments
...to print asm comments for spill information.
> > We've discussed the mechanisms before but I wanted to run the
> > patch by everyone before I start to commit pieces.
>
> Some thoughts:
>
> The general approach to enhancing CreateStackObject and adding
> MachineInstr::AsmPrinterFlags seems fine to me!
Ok.
> The testcase should use filecheck to avoid running llc 4 times. Also,
> it seems better to design a situation where you just have 16 live
> variables instead of taking some random function for gcc (you're
> implicitly depending on how ra is handling this...
2009 Aug 01
0
[LLVMdev] RFC: MachineInstr Annotations
On Jul 31, 2009, at 11:17 AM, David Greene wrote:
> I'm getting to the point where I want to contribute some more
> MachineInstr comment support for things like spills. As we've
> discussed before, we don't have all of the information available
> in AsmPrinter to synthesize the kind of comments that can be
> helpful for debugging performance issues with register
2009 Jul 31
3
[LLVMdev] RFC: MachineInstr Annotations
I'm getting to the point where I want to contribute some more
MachineInstr comment support for things like spills. As we've
discussed before, we don't have all of the information available
in AsmPrinter to synthesize the kind of comments that can be
helpful for debugging performance issues with register allocators
(our primary use for these kinds of comments).
In order to get this