Displaying 4 results from an estimated 4 matches for "jitstream".
Did you mean:
bitstream
2010 Apr 16
2
[LLVMdev] Intro to the MC Project
...the other pieces probably fall into place as it becomes obvious if they are needed.
It should be pretty straightforward to bring up something which works for running code with no external symbols, if you want to start this, I would recommend just trying to write the JITObjectWriter (and matching MCJITStreamer), and see where it goes. You can clone most of the Mach-O streamer for use by the JITStreamer, and gut the obviously unneeded parts. Once we have something working, we can factor out a common MCObjectStreamer class. I have been meaning to do this, but won't have time for a couple weeks I susp...
2010 Apr 17
0
[LLVMdev] Intro to the MC Project
...- Currently I'm using the LLVMTargetMachine::addPassesToEmitFile with
FileType set to CGFT_ObjectFile, and with the triple environment name hack,
I am able to create the correct streamer :
if (Triple(TargetTriple).getEnvironmentName().equals("JIT")) {
AsmStreamer.reset(createJITStreamer(*Context, *TAB, Out, MCE));
} else {
AsmStreamer.reset(createMachOStreamer(*Context, *TAB, Out, MCE));
}
What do you think ? Do you consider this to be acceptable ? Or just horrible
?
- MCObjectWriter::Write8 and MCObjectWriter::WriteBytes are designed to
write in a raw_ostream in...
2010 Apr 15
0
[LLVMdev] Intro to the MC Project
...s,
>
> Thanks for taking time to communicate on this.
Sorry I missed responding to this email sooner.
> In your open points, you speak about upgrading the JIT code path. If I want to take a look (or at least try...) on it, what would be the "roadmap" ?
>
> I assume, a MCJITStreamer is needed.
> And probably a JITObjectWriter (inherits from MCObjectWriter) and an associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ?
>
> What would be the chaining of calls ? The JITObjectWriter::WriteObject is called via the AsmPrinter::doFinalization. But how the Asm...
2010 Apr 11
2
[LLVMdev] Intro to the MC Project
Hi Chris,
Thanks for taking time to communicate on this.
In your open points, you speak about upgrading the JIT code path. If I want
to take a look (or at least try...) on it, what would be the "roadmap" ?
I assume, a MCJITStreamer is needed.
And probably a JITObjectWriter (inherits from MCObjectWriter) and an
associated TargetAsmBackend specific to the JIT (JITX86AsmBackend) ?
What would be the chaining of calls ? The JITObjectWriter::WriteObject is
called via the AsmPrinter::doFinalization. But how the AsmPrinter will be...