[llvm-commits] [PATCH] Generate info about the JIT process

Evan Cheng evan.cheng at apple.com
Tue May 12 18:56:07 PDT 2009

On May 11, 2009, at 7:03 PM, Evan Phoenix wrote:

>> Wow another Evan. :-)
> Doin' my part to raise the quota!
>> This looks fine but is it necessary? Can we just use
>> MachineCodeEmitter to report these? Should it be under
>> ExecutionEngine or CodeGen? Are you expecting to extend it to track
>> more information?
> After talking with a number of people in #llvm, this was the solution
> we came up with.  We couldn't come up with a solution for reporting
> the info from MachineCodeEmitter that didn't require restructuring
> things a lot, so this was the idea we came up with.


> One upside is that because it's isolated, we have the ability to
> easily extend it to track more information. One thing I eventually
> want to report is the Relocation information, so that the machine code
> can be manipulated outside of LLVMs control.
> I consider it to be a phase 1 of http://wiki.llvm.org/Provide_more_control_over_and_access_to_JIT%27s_output
> , which Jeffrey Yasskin and I have been discussing.
> So I guess my point is that I'm open to reporting this data a
> different way, but we haven't yet seen one that is as simple. :)

Ok. My only real complain about the patch is MachineCodeInfo.h should  
be in CodeGen just like MachineCodeEmitter.


> Additionally, I'm happy to craft this patch externally, but I think it
> would make everyones life easier to get it into the repo, so that
> others can work on adding things to the API.
>> Evan
> Also Evan
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits

More information about the llvm-commits mailing list