Displaying 3 results from an estimated 3 matches for "d5683".
Did you mean:
5683
2014 Oct 12
3
[LLVMdev] whole program optimization examples?
...iting your own GC is going to be a pain.
>>
> Out of curiosity, where did you hear this?
>
> We are actively working on improving the state of the world here. I'd
> suggest you take a look at the infrastructure patches currently up for
> review here: http://reviews.llvm.org/D5683
>
> These will hopefully land within a week or two. At that point, the "gc
> infrastructure" part should be functional. You'd have to pick a GC (LLVM
> does not provide one), but you're frontend could emit barriers and
> statepoints (gc parseable callsites) and ev...
2014 Oct 27
2
[LLVMdev] LLVM Weekly - #43, Oct 27th 2014
...on of statepoints vs
gcroot](http://www.philipreames.com/Blog/2014/10/21/statepoints-vs-gcroot-for-representing-call-safepoints/)
for representing call safepoints. The aim is to clearly explain how the
safepoint functionality provided by the [patches currently up for
review](http://reviews.llvm.org/D5683) differ to the current gc.root support.
The Haskell community have put together a [proposal for an improved LLVM
backend to GHC](https://ghc.haskell.org/trac/ghc/wiki/ImprovedLLVMBackend).
They intend to ship GHC with its own local LLVM build.
CoderGears have published a blog post about [using Cl...
2014 Oct 11
7
[LLVMdev] whole program optimization examples?
Hello,
I was wondering if there is an example list somewhere of whole program
optimizations done by LLVM based compilers?
I'm only familiar with method-level optimizations, and I'm being told wpo
can deliver many great speedups.
My language is currently staticly typed JIT based and uses the JVM, and I
want to move it over to LLVM so that I can have options where it can be
ahead of time