search for: mymcstreamer

...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 predefined set of final passes instead of free choice. AFAIK to get object code file I have to feed emitted code through my own MyMCStreamer class. The only sane option I see is to take assembly output from AsmStreamer (.s file) then feed it to AsmParser passing MyMCStreamer in AsmParser's constructor. Thus we've got instructions -> AsmPrinter -> AsmParser -> MyMCStreamer While ideally it should be only instruction...

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

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

...got predefined set > of final passes instead of free choice. LLVM 2.7 doesn't have final support for this. The idea is that we'd add ELF and PECOFFStreamers as well, or parameterize it a different way. > AFAIK to get object code file I have to feed emitted code through my own > MyMCStreamer class. The only sane option I see is to take assembly > output from AsmStreamer (.s file) then feed it to AsmParser passing > MyMCStreamer in AsmParser's constructor. You're going to have to hack up the code generator to do this in 2.7 -Chris