On Sat, Aug 24, 2013 at 5:23 AM, David Jeske <[email protected]> wrote:
> On Fri, Aug 23, 2013 at 12:35 PM, Jonathan S. Shapiro <[email protected]>wrote: > >> The first objective is to validate and bootstrap the *language*. There >> is a *lot* of infrastructure that needs to be built before any sort of >> production-capable implementation becomes possible. The more of that we can >> do in BitC itself, the happier we are going to be. But in order to do that, >> we need to have a running version of BitC to bootstrap in. The less >> investment we need to make in order to have a bootstrap implementation, the >> better. CLR is merely a collection of features that facilitate a bootstrap >> implementation. Nothing more. >> > > Unsurprisingly, I'm 110% in support of this direction. > If you think you will create or await a new jit runtime then any design decision that requires a feature not supported by the CLR can wait till the the new runtime is created / built first ... which should be a huge time saving ;-p Im not really convinced by the JIT model anymore ..the promised optomizations seem to have stalled or require so much time to work out that its inpractical to use in a JIT . Creating jit compilers or jit generating SIMD seems difficult and there are few open source ones. The main issues with static seem to be overcome in C++/CX ( runtime generics instead of templates, metadata) . I static creates issues with typing as has been discussed . That said the existing C++ could go onto the CLR via managed C++ very quick ... and the fact you dont have to worry about writng the GC , you have a huge lib ( which can hopefully be used / mapped) and on windows it will perform very well quickly is a huge win .. No requirements to worry about which the CLR doesnt support. These are huge practical wins so i support this as well despite my desire for something that creates libs i can call from native code. Regarding LLVM .. not tracking type information for registers - does any decent compiler after it goes through all the optimnization stages ? Mono uses LLVM so how critical is it ? Ben
_______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
