Displaying 4 results from an estimated 4 matches for "myobjectcodewrit".
Did you mean:
myobjectcodewriter
2010 Mar 27
2
[LLVMdev] Static code generation - is it gone from LLVM 2.7?
...you'd have to do that.
Ok, I'm trying to compile LLVM bytecode into some native object code
format. The thing very close to
> llc -filetype=obj foo.bc
To do so I mimic llc behaviour: create TargetMachine, create
FunctionPassManager, call TargetMachine::addPassesToEmitFile(), add my
own MyObjectCodeWriter pass and run passes.
But since LLVM 2.7 TargetMachine::addPassesToEmitFile (as implemented in
LLVMTargetMachine child class) adds its own final pass (AsmPrinter)
paired with either AsmStreamer, MachOStreamer or NullStreamer. I cannot
pass my own descendant of MCStreamer class. Now we've got...
2010 Mar 29
0
[LLVMdev] Static code generation - is it gone from LLVM 2.7?
...k, I'm trying to compile LLVM bytecode into some native object code
> format. The thing very close to
>> llc -filetype=obj foo.bc
>
> To do so I mimic llc behaviour: create TargetMachine, create
> FunctionPassManager, call TargetMachine::addPassesToEmitFile(), add my
> own MyObjectCodeWriter pass and run passes.
>
> But since LLVM 2.7 TargetMachine::addPassesToEmitFile (as implemented in
> LLVMTargetMachine child class) adds its own final pass (AsmPrinter)
> paired with either AsmStreamer, MachOStreamer or NullStreamer. I cannot
> pass my own descendant of MCStreamer...
2010 Mar 27
0
[LLVMdev] Static code generation - is it gone from LLVM 2.7?
On Mar 27, 2010, at 12:49 PM, Peter Shugalev wrote:
>>>
>>> New method of emitting object code is ok for me. But it is still
>>> experimental, isn't it?
>>
>> Yes.
>
> Thank you for answers!
>
> Now there is a way to implement what I'd like to. But it would be MUCH
> better if LLVMTargetMachine::addPassesToEmitFile could take
2010 Mar 27
3
[LLVMdev] Static code generation - is it gone from LLVM 2.7?
Chris Lattner wrote:
> On Mar 27, 2010, at 11:56 AM, Peter Shugalev wrote:
>
>>>> What exactly is expected to be coming? Will it be the same way MachO is
>>>> currently implemented but with some flexibility to supply my own class
>>>> to do actual object output? Or just a return of old ObjectCodeEmitter?
>>> We're integrating a full assembler