Displaying 3 results from an estimated 3 matches for "readbarri".
Did you mean:
readbarrier
2009 Jun 02
1
[LLVMdev] RFC: Atomics.h
On Jun 1, 2009, at 11:17 PM, Jonathan Ragan-Kelley wrote:
> Yes, indeed.
Are they macros or functions? If macros, why not just #undef them at
the top of Atomics.h?
-Chris
>
>
> On May 28, 10:41 pm, Owen Anderson <resis... at mac.com> wrote:
>>
>> Wait, it defines MemoryFence() AND MemoryBarrier()??
>>
>> Sheesh, they had to take all the reasonable
2008 Apr 22
0
[LLVMdev] getting closer!
...More elaboration is inline.
Ephemeral temporaries get gcroots. This could be unnecessary for a
single-threaded collector if the temp isn't alive across a call.
Each use of a reference variable or temp is reloaded from the gcroot.
This is necessary only for copying collectors.
However, @llvm.readbarrier and @llvm.writebarrier are not used. Using
them would be more conservative still, but quite verbose.
; This is the runtime-defined type for class metadata.
; Here, it contains only GC tracing information.
;
; namespace runtime {
; class Class {
; unsigned NumReferences;
; struct {
;...
2008 Apr 22
2
[LLVMdev] getting closer!
On Apr 21, 2008, at 6:23 PM, Gordon Henriksen wrote:
> On Apr 21, 2008, at 20:09, Terence Parr wrote:
>
>> Ok, I *might* be getting this from the assembly code. ... From
>> that, it will push/pop in functions? If so, that's easy enough. :)
>
> Yup! Sounds like you've got it.
Yup, what i was missing and what somebody should add to the doc is
that