Displaying 4 results from an estimated 4 matches for "numimplicitop".
Did you mean:
numimplicitops
2009 Jul 31
3
[LLVMdev] RFC: MachineInstr Annotations
...the AsmPrinter without requring
a lot of overhead, I'd like to propose adding a small bitvector to
MachineInstr to hold flags. Something like this:
class MachineInstr : public ilist_node<MachineInstr> {
const TargetInstrDesc *TID; // Instruction descriptor.
unsigned short NumImplicitOps; // Number of implicit operands (which
// are determined at construction
time).
unsigned short Flags; // ***NEW*** Various bits of info
std::vector<MachineOperand> Operands; // the operands
std::list<MachineMemOperand...
2009 Aug 01
0
[LLVMdev] RFC: MachineInstr Annotations
...uring
> a lot of overhead, I'd like to propose adding a small bitvector to
> MachineInstr to hold flags. Something like this:
>
> class MachineInstr : public ilist_node<MachineInstr> {
> const TargetInstrDesc *TID; // Instruction descriptor.
> unsigned short NumImplicitOps; // Number of implicit
> operands (which
> // are determined at
> construction
> time).
>
> unsigned short Flags; // ***NEW*** Various bits of
> info
Those bits are almost asking to be used ;-).
>
>...
2009 Jul 14
0
[LLVMdev] [PATCH] Support asm comment output
On Monday 13 July 2009 15:58, David Greene wrote:
> Again, after answering the FI stack slot question, the IR-level instruction
> information is the only thing we can't do through asmprinter. I'm open to
> other ways of capturing the information that don't require comments in
> MachineInstrs. But the information has to be stored somewhere.
Ugh. I just found another
2009 Jul 13
5
[LLVMdev] [PATCH] Support asm comment output
On Monday 13 July 2009 15:46, Chris Lattner wrote:
> Well sure, but how is that relevant? Just generate llvm.stoppoint and
> isel turns them into debug locs. Just because debugloc isn't on
> llvm::Instruction doesn't mean you don't get line numbers :).
You're right, it's not a big hurdle.
> > Ok, here's an example:
> >
> > movl