On Friday, 31 March 2017 at 14:16:15 UTC, Stefan Koch wrote:
On Friday, 31 March 2017 at 14:05:00 UTC, Stefan Koch wrote:
On Thursday, 16 February 2017 at 21:05:51 UTC, Stefan Koch
wrote:
[ ... ]
Alright guys.
I am just fixing the newCTFE LLVM backend such that I can have
better guesses as to what performance a JIT could archive.
Due to the ABI changes the llvm-backend a little optimization
potential.
It'll be a while until the llvm backend is on par again.
Because functions and such need to be dealt with quite
differently.
Also the llvm backend recives less testing since I cannot run
it at compile time(Yet :))
Cheers,
Stefan
--
sorry for the short message I am busy fixing codegen bugs as
always.
oh, yeah ... If you want to checkout the llvm backend fethc the
newCTFE_LLVMBackend branch from
https://github.com/UplinkCoder/dmd.
the posix.mak is hardcoded to use libLLVM-3.5.
However you should be able to use any version newer then 3.3.
How far off until newCTFE is usable to compile the majority of
templates out there? I have some new code that doesn't do
anything real complex but seems quite slow for no apparent reason
and would like to try the newCTFE if it has a good chance of
working.
