search for: xxxinstprint

Hi, LLVMers, I notice that there are two versions of printInstruction() generated by tablegen: (1) XXXInstPrinter::printInstruction(const MCInst *MI, raw_ostream &os), like for X86. (2) XXXAsmPrinter::printInstruction(const MachineInstr *MI, raw_ostream &os), like for Sparc. I guess Sparc backend directly transform MachineInstr objects into ostream, while X86 backend convert MachineInstr into MCInst...

...dually depend on all the real features: + RxTargetMachine.cpp is small, but central. It's where you register the passes that actually do the work. If you can get things to compile with these functions doing their job you should have stubs for most of the necessary components. + InstPrinter/XXXInstPrinter.cpp: This is the main entry for the so-called MC instruction printing, which is the good way to do things. It's theoretically possible to get your instructions printing without creating this, but you'd be Doing It Wrong. But most importantly, have fun and don't be afraid to ask more...

Hi all, llvm newbie here. I'm trying to learn porting with llvm for study purpose. This is my first query on llvm mailing list.I have some idea about GCC. I choose 'rx' as a target to port as it is also available in GCC. I have done some initial changes with llvm source code to register target with llvm. I need to verify these changes. Can anyone please take a chance to verify it.

...> features: > + RxTargetMachine.cpp is small, but central. It's where you register > the passes that actually do the work. If you can get things to compile > with these functions doing their job you should have stubs for most of > the necessary components. > + InstPrinter/XXXInstPrinter.cpp: This is the main entry for the > so-called MC instruction printing, which is the good way to do things. > It's theoretically possible to get your instructions printing without > creating this, but you'd be Doing It Wrong. > > But most importantly, have fun and don'...