Displaying 2 results from an estimated 2 matches for "tp22704803p22708428".
2009 Mar 25
0
[LLVMdev] Rolling my own LLVM assembly language parser
You can achieve the 'standalone tools' effect using LLVM bitcode,
which is a binary IR format.
Then you can have:
source code -> [llvm-gcc frontend] -> bc
bc -> [your tool using llvm bitcode reader writer library, doing
whatever mutations to the IR you want and spitting out bc again] -> bc
bc -> [llvm backend (llc)/llvm-as/...] -> native code.
Doesn't that meet your
2009 Mar 25
2
[LLVMdev] Rolling my own LLVM assembly language parser
Thank you both for your answers.
The only reason I was interested in not using the built-in parsing library
was that it would give me more flexibility over the language I program in,
but if it means brushing up on my C++ then this isn't too much of a problem
either.
With regards to using the in-memory LLVM, that's also a good approach.
However, I was thinking of structuring my thesis