search for: initial_valu

...ing the constraint "pointers to heap objects are invalidated at every safepoint" somehow in the IR itself. So, if %a and %b are values the GC is interested in, the safepoint at the back-edge of a loop might look like: ; <label>: body %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] ;; Use %a and %b ;; The safepoint starts here %a.relocated = @llvm.gc_relocate(%a) %b.relocated = @llvm.gc_relocate(%b) br %body This allows us to not bother with relocating derived pointers pointin...

On Oct 24, 2013, at 2:50 PM, Rafael Espíndola <rafael.espindola at gmail.com> wrote: > On 24 October 2013 17:32, Sanjoy Das <sanjoy at azulsystems.com> wrote: >> Hello llvm-dev! >> >> My colleages and I are currently evaluating llvm's suitability as a >> JIT compiler interfacing with a precise, relocating garbage collector. >> While we

Hi all, I was wondering about the class used when rails receives file uploads. Sometimes it appears to be a File, and other times it is a StringIO. Also it has methods such as original_filename that don''t appear to belong to either of these classes. I ask because I''m trying to work out how to test my fil upload related models and controllers. Is there some standardised way of

...ters to heap objects are invalidated at every > safepoint" somehow in the IR itself. So, if %a and %b are values the > GC is interested in, the safepoint at the back-edge of a loop might > look like: > > ; <label>: body > %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] > %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] > ;; Use %a and %b > > ;; The safepoint starts here > %a.relocated = @llvm.gc_relocate(%a) > %b.relocated = @llvm.gc_relocate(%b) > br %body > > This allows us to not both...

...are invalidated at every > safepoint" somehow in the IR itself. So, if %a and %b are values the > GC is interested in, the safepoint at the back-edge of a loop might > look like: > > ; <label>: body > %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] > %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] > ;; Use %a and %b > > ;; The safepoint starts here > %a.relocated = @llvm.gc_relocate(%a) > %b.relocated = @llvm.gc_relocate(%b) > br %body > >...

...invalidated at every >> safepoint" somehow in the IR itself. So, if %a and %b are values the >> GC is interested in, the safepoint at the back-edge of a loop might >> look like: >> >> ; <label>: body >> %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] >> %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] >> ;; Use %a and %b >> >> ;; The safepoint starts here >> %a.relocated = @llvm.gc_relocate(%a) >> %b.relocated = @llvm.gc_relocate(%b) >> br %body >>...

...invalidated at every >> safepoint" somehow in the IR itself. So, if %a and %b are values the >> GC is interested in, the safepoint at the back-edge of a loop might >> look like: >> >> ; <label>: body >> %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] >> %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] >> ;; Use %a and %b >> >> ;; The safepoint starts here >> %a.relocated = @llvm.gc_relocate(%a) >> %b.relocated = @llvm.gc_relocate(%b) >> br %body >>...

...in the IR itself. So, if %a and %b are values the >>>> GC is interested in, the safepoint at the back-edge of a loop might >>>> look like: >>>> >>>> ; <label>: body >>>> %a = phi i32 [ %a.relocated, %body ] [ %a.initial_value, %pred ] >>>> %b = phi i32 [ %b.relocated, %body ] [ %b.initial_value, %pred ] >>>> ;; Use %a and %b >>>> >>>> ;; The safepoint starts here >>>> %a.relocated = @llvm.gc_relocate(%a) >>>> %b.relocated = @ll...