[LLVMdev] Taking over work on CodeExtractor, spiffing it up, and making it nice & easy to use

[Chandler Carruth]

On Wed, May 2, 2012 at 1:57 AM, Dmitry N. Mikushin <maemarcus at gmail.com>wrote:

> At KernelGen we have an out-of-tree variation of CodeExractor called
> BranchedCodeExractor [1], which instead of taking a code region into a new
> function, does it conditionally:
>

OK... as this is an out-of-tree branch of the code extraction, nothing I'm
planning should negatively impact it... I don't know your use case, so I
don't have any specific changes that would likely help you out, but if
there are changes you would like to see to the core code extractor in LLVM,
feel fere to propose patches...


>
> ORIGINAL_CODE;
>
> ->>
>
> if (extracted_code_function(args) != -1)
> {
>    ORIGINAL_CODE;
> }
>
> I think many hybrid and parallelizing tools need the same logic. For
> instance, LLVM Polly should be using a very similar code exractor for
> OpenMP backend.
>

I'll check Polly to make sure it's not directly using these interfaces...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120502/91004c24/attachment.html>