Displaying 2 results from an estimated 2 matches for "polyinstantate".
2008 Mar 26
4
[LLVMdev] Hooking the global symbol resolver
Okay, we're starting to dig in, and I've hit a question that will no
doubt seem strange.
Context: BitC is a polymorphic language. Since it has unboxed value
types, our approach to compiling a polymorphic function is to
polyinstantate it -- once for each signature.
The name mangling scheme is both stable and reversible. At the site of
the use occurrence, we can fully determine the mangled name of the
desired instantiation. Given the mangled name of an instantiation that
has not yet been synthesized, we can determine which proce...
2008 Mar 27
0
[LLVMdev] Hooking the global symbol resolver
...t 17:07, Jonathan S. Shapiro wrote:
> Okay, we're starting to dig in, and I've hit a question that will no
> doubt seem strange.
>
> Context: BitC is a polymorphic language. Since it has unboxed value
> types, our approach to compiling a polymorphic function is to
> polyinstantate it -- once for each signature.
>
> The name mangling scheme is both stable and reversible. At the site
> of the use occurrence, we can fully determine the mangled name of
> the desired instantiation. Given the mangled name of an
> instantiation that has not yet been synthesized...