[haskell-llvm] llvm-base vs. llvm-general

[Carter Schonwald]

henning, I understand your stance, what i'm saying is I am happy to
evaluate porting the llvm api to sit on top of llvm-general. If it was api
compatible, would that be a satisfactory type safebackend?


On Sat, Jan 18, 2014 at 5:59 PM, Henning Thielemann <
schlepptop at henning-thielemann.de> wrote:

> Am 18.01.2014 23:43, schrieb Carter Schonwald:
>
>  Hey Henning,
>>
>> Nathan has examples of an "llvm" style, albeit modernized / cleaned
>> variant on top of llvm-general
>> https://github.com/alphaHeavy/llvm-general-typed, though some
>> contributions are probably still needed to bring it to full parity.
>>
>
> thanks for the pointer
>
>
>
>  The fact of the matter is that llvm-base is tightly wedded to the llvm c
>> API, and doesn't have a clear extensibility story to handle features
>> supported that are only exposed via the c++ api
>>
>>
>> That said, you do raise a  good point, that for support reasons,
>> updating the old style llvm api to use llvm general rather than llvm
>> base is worth considering. I may spend some time swapping llvm-general
>> in for llvm-base and seeing how that works out.
>>
>
>
> I didn't want to request an overhaul or partial transition of
> llvm-base/llvm to llvm-general. For me the LLVM-C API is almost enough, I
> do not need an LLVM AST or LLVM syntax transformation. I need LLVM for
> speeding up my Haskell code, that is I need a JIT that I can invoke simply,
> quickly and (type) safely.
>
> I only wish, that if actually all former maintainers of the llvm package
> moved to llvm-general then it would be nice to officially mark the package
> as orphaned plus you may call for a new maintainer. I have thought about
> continuing the llvm-base/llvm approach myself, but I would certainly
> refactor it a lot and then it may be better called a fork.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://projects.haskell.org/pipermail/haskell-llvm/attachments/20140118/ded8ffe4/attachment.htm>