[llvm-commits] [patch] Identifying code sections in MCJIT

Michael Spencer bigcheesegs at gmail.com
Mon Dec 17 08:48:46 PST 2012


On Mon, Dec 17, 2012 at 6:18 AM, Tim Northover <t.p.northover at gmail.com> wrote:
> On Fri, Dec 14, 2012 at 6:22 PM, Jim Grosbach <grosbach at apple.com> wrote:
>> Just poking my nose in to confirm that looking the pure-instructions flag is a good
>> way to go. Andy, echristo and I chatted about this on IRC a bit the other day.
>
> Ok. I'm rather stumbling around in the dark here, but I've had a go at
> using the suggested flag on MachO. If anything more sophisticated than
> this is needed, I'll either need to be told what or someone else will
> have to do it.
>
> Correct me if I'm wrong, but using the MC flag definition from Object
> would be a layering violation, wouldn't it? Assuming so, the flag
> needs to be defined in MachOFormat.h (with an odd name to fit in with
> existing use there).
>
> I've attached two separate patches: the first changes MachO and the
> second is identical to before. Ok to commit them?
>
> Regards.
>
> Tim.
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>

Both patches LGTM.

- Michael Spencer



More information about the llvm-commits mailing list