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

[Tim Northover]

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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: macho-text-definition.diff
Type: application/octet-stream
Size: 2555 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20121217/555e2191/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: identify-code-section.diff
Type: application/octet-stream
Size: 1513 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20121217/555e2191/attachment-0001.obj>