search for: _loading_

...StringBuffer sb = new StringBuffer(); // Is 'this' still live at this point? sb.append(toString()); } } Now, I know that the LLVM "Accurate GC" document says that any "intermediate values" must be declared as a GC root. My question is, does merely _loading_ a global variable - or any mutable, non-strictly-local variable for that matter - count as an "intermediate" value in this case? My problem is that I can't see how to address this without generating horribly bloated and inefficient code. Pretty much every function argument that isn...

So I've managed to get my stack crawler working and passing its unit tests - this is the one I've been working on as an alternative to shadow-stack: it uses only static constant data structures (no global variables or thread-local data), which means that it's fully compatible with a multi-threaded environment. One question that has arisen, however, is what to do about function

...x, include.only="fac2sparse") > >> > library(Matrix) > >> > ls("package:Matrix") > >> > # [1] "fac2sparse" > >> > >> > ?library does not cover this case -- what is covered is the > >> _loading_ > >> > behavior of repeated calls: > >> > >> >> [library and require] check and update the list of currently > >> attached > >> > packages and do not reload a namespace which is already loaded > >> > >> &...

Right now, attaching the same package with different include.only= has no effect: library(Matrix, include.only="fac2sparse") library(Matrix) ls("package:Matrix") # [1] "fac2sparse" ?library does not cover this case -- what is covered is the _loading_ behavior of repeated calls: > [library and require] check and update the list of currently attached packages and do not reload a namespace which is already loaded But here we're looking at the _attach_ behavior of repeated calls. I am particularly interested in allowing the exports of a p...

...sparse") >> >> > library(Matrix) >> >> > ls("package:Matrix") >> >> > # [1] "fac2sparse" >> >> >> >> > ?library does not cover this case -- what is covered is the _loading_ >> >> > behavior of repeated calls: >> >> >> >> >> [library and require] check and update the list of currently attached >> >> > packages and do not reload a namespace which is already loaded >> &gt...

...in, yes, if f1 copied the result of "new Foo()" into a root. >       sb.append(toString()); >     } >   } > Now, I know that the LLVM "Accurate GC" document says that any "intermediate > values" must be declared as a GC root. My question is, does merely _loading_ > a global variable - or any mutable, non-strictly-local variable for that > matter - count as an "intermediate" value in this case? Yes, I believe it would. In a multithreaded system, if you load a pointer from a global or the heap, and some other thread changes the pointer you l...

...ot;new Foo()" into a root. > > > sb.append(toString()); > > } > > } > > Now, I know that the LLVM "Accurate GC" document says that any > "intermediate > > values" must be declared as a GC root. My question is, does merely > _loading_ > > a global variable - or any mutable, non-strictly-local variable for that > > matter - count as an "intermediate" value in this case? > > Yes, I believe it would. In a multithreaded system, if you load a > pointer from a global or the heap, and some other thread c...