Displaying 5 results from an estimated 5 matches for "printregname".
Did you mean:
printername
2011 Jul 06
0
[LLVMdev] MCInstPrinter::printRegName
...ing Machine IR layer to MC layer lowering for Mips.
What's the best way to print the value of "Register" in the following code
in MCAsmStreamer::EmitRegisterName? Do I have to convert the LLVM register
number back to its corresponding dwarf register number in function
InstPrinter->printRegName? I just want to have it output the same register
number as before (the same output the false path would produce).
void MCAsmStreamer::EmitRegisterName(int64_t Register) {
if (InstPrinter) {
const TargetAsmInfo &asmInfo = getContext().getTargetAsmInfo();
unsigned LLVMRegister = asmInf...
2013 Oct 28
2
[LLVMdev] Are Opcode and register mappings exposed anywhere?
...option is to use MCInstPrinter::getOpcodeName and compare strings. (Of course, I could iterate through the opcodes and build up a table of the ones I'm interested in to avoid string comparisons.)
Register mappings to names seem to be even worse. It appears you have to go through MCInstPrinter::printRegName(raw_ostream&, unsigned).
Is there a better way?
--
Stephen Checkoway
2013 Oct 28
0
[LLVMdev] Are Opcode and register mappings exposed anywhere?
...rinter::getOpcodeName and compare strings. (Of course, I
> could iterate through the opcodes and build up a table of the ones I'm
> interested in to avoid string comparisons.)
>
> Register mappings to names seem to be even worse. It appears you have to
> go through MCInstPrinter::printRegName(raw_ostream&, unsigned).
>
> Is there a better way?
>
> --
> Stephen Checkoway
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mail...
2013 Oct 28
2
[LLVMdev] Are Opcode and register mappings exposed anywhere?
...to use MCInstPrinter::getOpcodeName and compare strings. (Of course, I could iterate through the opcodes and build up a table of the ones I'm interested in to avoid string comparisons.)
>
> Register mappings to names seem to be even worse. It appears you have to go through MCInstPrinter::printRegName(raw_ostream&, unsigned).
>
> Is there a better way?
>
> --
> Stephen Checkoway
>
>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.ed...
2013 Oct 29
0
[LLVMdev] Are Opcode and register mappings exposed anywhere?
...tOpcodeName and compare strings. (Of course, I
> could iterate through the opcodes and build up a table of the ones I'm
> interested in to avoid string comparisons.)
> >
> > Register mappings to names seem to be even worse. It appears you have to
> go through MCInstPrinter::printRegName(raw_ostream&, unsigned).
> >
> > Is there a better way?
> >
> > --
> > Stephen Checkoway
> >
> >
> >
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu...