Displaying 6 results from an estimated 6 matches for "llvmgcroot".
2008 Jan 07
2
[LLVMdev] GC infrastructure checked in
...ogram must provide the
stack walker (in addition to the GC), so complete GC programs are
nontrivial. This is somewhat similar to the state of exception
handling in LLVM. It would be an excellent project to provide
reference implementations of these facilities.
That said, the PyPy group has llvmgcroot support on a branch; you
could ask Armin Rigo <arigo at tunes dot org> for details about
accessing it.
On his benchmarks, Armin saw an 8% speedup vs. a shadow stack. Their
gcc backend still outperforms the LLVM backend, though—and llvm-gcc
outperforms that further still. So perhaps t...
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
...stack walker (in addition to the GC), so complete GC programs are
> nontrivial. This is somewhat similar to the state of exception
> handling in LLVM. It would be an excellent project to provide
> reference implementations of these facilities.
>
> That said, the PyPy group has llvmgcroot support on a branch; you
> could ask Armin Rigo <arigo at tunes dot org> for details about
> accessing it.
>
> On his benchmarks, Armin saw an 8% speedup vs. a shadow stack. Their
> gcc backend still outperforms the LLVM backend, though—and llvm-gcc
> outperforms tha...
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
On Monday 07 January 2008 02:32:47 Gordon Henriksen wrote:
> Everything described in GarbageCollection.html should now be live. Phew!
>
> The collectors could use a review, but they compile, have no impact
> unless used, and tests would otherwise have had to be XFAILed waiting
> on them.
>
> The ShadowStackCollector has one issue that may be of interest in that
> it adds
2008 Jan 07
0
[LLVMdev] GC infrastructure checked in
Hello, Everyone
> That said, the PyPy group has llvmgcroot support on a branch; you
> could ask Armin Rigo <arigo at tunes dot org> for details about
> accessing it.
FYI: some status report can be seen here:
http://codespeak.net/pipermail/pypy-dev/2008q1/004441.html
--
WBR, Anton Korobeynikov
2008 Jan 07
2
[LLVMdev] GC infrastructure checked in
On Jan 7, 2008, at 10:54, Carl Friedrich Bolz wrote:
> Gordon Henriksen wrote:
>
>> That said, the PyPy group has llvmgcroot support on a branch; you
>> could ask Armin Rigo <arigo at tunes dot org> for details about
>> accessing it.
>>
>> On his benchmarks, Armin saw an 8% speedup vs. a shadow stack.
>> Their gcc backend still outperforms the LLVM backend, though—and
>>...
2008 Jan 07
3
[LLVMdev] GC infrastructure checked in
Everything described in GarbageCollection.html should now be live. Phew!
The collectors could use a review, but they compile, have no impact
unless used, and tests would otherwise have had to be XFAILed waiting
on them.
The ShadowStackCollector has one issue that may be of interest in that
it adds constant globals in a runOnFunction context. This is bad in
theory, but actually is