search for: int_or_str

...my compiler, what I do is to generate a callback function that can trace > the object. This callback function is contained within a data structure that > is passed as the metadata argument to llvm.gcroot. > > So my code looks like this (bit casts omitted for simplicity): > > %int_or_string = type { i8, String * } > %x = alloca %int_or_string > call void llvm.gcroot( i8 ** x, i8* @.tracetable.int_or_string) > > Where '.tracetable.int_or_string' is the static type information for the > "int or string" type, containing both the field offsets a...

...ntains a pointer or not. In my compiler, what I do is to generate a callback function that can trace the object. This callback function is contained within a data structure that is passed as the metadata argument to llvm.gcroot. So my code looks like this (bit casts omitted for simplicity): %int_or_string = type { i8, String * } %x = alloca %int_or_string call void llvm.gcroot( i8 ** x, i8* @.tracetable.int_or_string) Where '.tracetable.int_or_string' is the static type information for the "int or string" type, containing both the field offsets and the callback function...

...is to generate a callback function that can >> trace the object. This callback function is contained within a data >> structure that is passed as the metadata argument to llvm.gcroot. >> >> So my code looks like this (bit casts omitted for simplicity): >> >> %int_or_string = type { i8, String * } >> %x = alloca %int_or_string >> call void llvm.gcroot( i8 ** x, i8* @.tracetable.int_or_string) >> >> Where '.tracetable.int_or_string' is the static type information for the >> "int or string" type, containing both...

Hi Talin, On Sat, Sep 25, 2010 at 4:18 AM, Talin <viridia at gmail.com> wrote: > > > Many languages support the notion of a "value type". Value types are always > passed by value, unlike reference types which are always passed by > pointer. An example is the "struct" type in C#. Another example is a "tuple" > type. A value type which is a