[PATCH][llvm-c] Expose MC JIT

[Eric Christopher]

There aren't any C API tests at the moment, but I'd definitely take
some if they were to appear :)

-eric

On Tue, Apr 23, 2013 at 1:37 AM, Kaylor, Andrew <andrew.kaylor at intel.com> wrote:
> I’m not sure one way or the other if there are any C API tests.  Unless
> someone has a better suggestion, I’d say this could go in the
> ‘unittests/ExecutionEngine’ tree, perhaps parallel to the MCJIT tests that
> are there.
>
>
>
> -Andy
>
>
>
> From: Filip Pizlo [mailto:fpizlo at apple.com]
> Sent: Monday, April 22, 2013 4:50 PM
> To: Kaylor, Andrew
> Cc: llvm-commits at cs.uiuc.edu
>
>
> Subject: Re: [PATCH][llvm-c] Expose MC JIT
>
>
>
>
>
>
> On Apr 22, 2013, at 4:43 PM, "Kaylor, Andrew" <andrew.kaylor at intel.com>
> wrote:
>
> Looks great!
>
>
>
> Any chance you have tests for this?
>
>
>
> Heh, good question. I tested it by running WebKit tests, but I can do
> better. Anything I should be mindful of when writing unit tests for the
> MCJIT?  And in particular the C API?  I couldn't immediately find we're C
> API tests lived.
>
>
>
>
>
> -Andy
>
>
>
> From: llvm-commits-bounces at cs.uiuc.edu
> [mailto:llvm-commits-bounces at cs.uiuc.edu] On Behalf Of Filip Pizlo
> Sent: Monday, April 22, 2013 2:09 PM
> To: llvm-commits at cs.uiuc.edu
> Subject: Re: [PATCH][llvm-c] Expose MC JIT
>
>
>
> Here it is.  The C API no longer exposes finalizeObject() in any way, and
> makes sure to call it prior to doing anything that the user would expect to
> have already done permissions/invalidation.
>
>
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>