On 30/03/2011 10:02 PM, Jonathan S. Shapiro wrote: > The first is that BitC > has inboard types, and this entails parametricity over sizes. If we > assume a dynamic compilation component, this admits multiple solutions. > If we require static compilation it seems hopeless.
Depends what you mean by "static compilation". Cyclone had a paper on dynamic code generation by stitching together code templates. You can support link time code generation using this technique using all native code. This looks pretty much like a static compilation pipeline, and doesn't require a special IR that can describe the full language in order to perform the code generation at link time. Sandro _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
