Displaying 3 results from an estimated 3 matches for "pseudoinstalpha".
2005 Apr 15
0
[LLVMdev] MachineInstr: external symbols problem
...while lowering the pcmarker intrinsic ;-)
> Need to get in to assembler somehow, and I already have a code that parses
> assembler and recognised calls to functions with certain name patterns as
> markers.
It looks like the Alpha backend treats these as pseudo instructions:
def PCLABEL : PseudoInstAlpha<(ops s64imm:$num), "PCMARKER_$num:\n">;
maybe you could do something similar? If not, I think the string table is
the way to go...
-Chris
--
http://nondot.org/sabre/
http://llvm.cs.uiuc.edu/
2005 Apr 15
3
[LLVMdev] MachineInstr: external symbols problem
On Friday 15 April 2005 18:49, Chris Lattner wrote:
> On Fri, 15 Apr 2005, Vladimir Prus wrote:
> > Hello,
> > I just wrote the code like this:
> >
> > BuildMI(BB, NM::CALL, 1)
> > .addExternalSymbol(("_lvksda_control_marker_"
> > +
> > lexical_cast<string>(bb)).c_str());
> >
2005 Apr 15
1
[LLVMdev] MachineInstr: external symbols problem
...> intrinsic ;-) Need to get in to assembler somehow, and I already have a
> > code that parses assembler and recognised calls to functions with certain
> > name patterns as markers.
>
> It looks like the Alpha backend treats these as pseudo instructions:
>
> def PCLABEL : PseudoInstAlpha<(ops s64imm:$num), "PCMARKER_$num:\n">;
Interesting trick. It looks like '$num' inside the string is interpreted
automatically. Is it matches with "$num" in the first argument? If the first
argument is DAG, will it work if my backend does not use pattern matchin...