I have had references to llvm-mc in terms of a tester for MC level code changes and have just found and read the blog http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html. Am I correct that lib/Target/<target>/AsmParser/*.cpp needs to be completed to make a standalone assembler for a specific target and until that is done, llvm-mc can't be used to generate output object that is tested by elf-dump? If this is correct, then is there any documentation on what to do or is there a preferred target that currently supports a standalone assembler as llvm-mc. I'm guessing that the answer is yes, I have to know how to parse the target specific assembly and maybe look at the ARM implementation for guidance. Cheers, Jack -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120112/f7a28640/attachment.html>
On Jan 11, 2012, at 6:05 PM, Carter, Jack wrote:> I have had references to llvm-mc in terms of a tester for MC level code changes and have just found and read the blog http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html. > > Am I correct that lib/Target/<target>/AsmParser/*.cpp needs to be completed to make a standalone assembler for a specific target and until that is done, llvm-mc can't be used to generate output object that is tested by elf-dump?You need to implement an AsmParser if you want to generate object files from assembly files. You can generate object files from higher-level inputs (.c, .ll) without a functional AsmParser as long as your inputs don't use inline assembly. --Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120111/676ba4c7/attachment.html>
We are already generating object directly. It is on my roadmap to implement the standalone assembler, but I was hoping for some suggestions ;-) My target is Mips and I have started looking at what ARM does. If there is a better model or how-to guide I'd like to know. Thanks, Jack ________________________________ From: Owen Anderson [resistor at mac.com] Sent: Wednesday, January 11, 2012 6:40 PM To: Carter, Jack Cc: List Subject: Re: [LLVMdev] llvm-mc standalone assemblers and testing On Jan 11, 2012, at 6:05 PM, Carter, Jack wrote: I have had references to llvm-mc in terms of a tester for MC level code changes and have just found and read the blog http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html. Am I correct that lib/Target/<target>/AsmParser/*.cpp needs to be completed to make a standalone assembler for a specific target and until that is done, llvm-mc can't be used to generate output object that is tested by elf-dump? You need to implement an AsmParser if you want to generate object files from assembly files. You can generate object files from higher-level inputs (.c, .ll) without a functional AsmParser as long as your inputs don't use inline assembly. --Owen -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120112/17f00a34/attachment.html>
Maybe Matching Threads
- [LLVMdev] llvm-mc standalone assemblers and testing
- [LLVMdev] llvm-mc standalone assemblers and testing
- [LLVMdev] llvm-mc standalone assemblers and testing
- [LLVMdev] llvm-mc standalone assemblers and testing
- [LLVMdev] (MC) Register parsing for AsmParser (standalone assembler)