Re: Please say hello to our third team member: Razvan Nitu

2016-10-18 Thread Uplink_Coder via Digitalmars-d-announce
On Tuesday, 18 October 2016 at 18:21:31 UTC, Andrei Alexandrescu wrote: Hi everyone, Please join me in welcoming Razvan Nitu to our fledgling team of Romanian graduate students. Razvan has already some solid industrial experience and has a broad area of interests such as low-level

Re: Battle-plan for CTFE

2016-10-17 Thread Uplink_Coder via Digitalmars-d-announce
On Monday, 17 October 2016 at 00:56:01 UTC, Uplink_Coder wrote: If anyone want to take a look the lastest llvm_backend development is happening here : https://github.com/UplinkCoder/dmd/blob/_ctfe/src/bc_llvm_backend.d The time llvm takes to build it's IR and execute the JITed code is

Re: Bug in header file generation

2016-10-17 Thread Uplink_Coder via Digitalmars-d
On Monday, 17 October 2016 at 08:03:18 UTC, Satoshi wrote: On Monday, 17 October 2016 at 07:54:33 UTC, Mike Parker wrote: On Monday, 17 October 2016 at 07:50:17 UTC, Satoshi wrote: On Saturday, 15 October 2016 at 06:55:31 UTC, Uplink_Coder wrote: On Saturday, 15 October 2016 at 06:51:44 UTC,

Re: Battle-plan for CTFE

2016-10-16 Thread Uplink_Coder via Digitalmars-d-announce
On Sunday, 16 October 2016 at 13:51:55 UTC, Uplink_Coder wrote: On Sunday, 16 October 2016 at 10:58:57 UTC, Dmitry Olshansky wrote: That LLVM thing is surely nice to have but I highly doubt it will be allowed as dependency for DMD. --- Dmitry Olshansky LLVM is purely optional. A pure D

Re: Reducing the cost of autodecoding

2016-10-16 Thread Uplink_Coder via Digitalmars-d
On Sunday, 16 October 2016 at 07:59:16 UTC, Patrick Schluter wrote: Here my version. It's probably not the shortest (100 ligns of assembly with LDC) but it is correct and has following properties: - Performance proportional to the encoding length - Detects Invalid byte sequences - Detects

Re: Battle-plan for CTFE

2016-10-16 Thread Uplink_Coder via Digitalmars-d-announce
On Wednesday, 5 October 2016 at 08:34:06 UTC, Rory McGuire wrote: No worries, I've been watching this space for over a decade. I really believe you are working on one of the most important parts of IT for the next decade. I am planning/making a library that uses CTFE extensively and feel

Re: core.intrinsics

2016-10-16 Thread Uplink_Coder via Digitalmars-d
On Saturday, 15 October 2016 at 10:17:09 UTC, Matthias Bentrup wrote: You could turn "hints" that can possibly create invalid code automatically into assertions in non-release builds. Or let the user add an assertion and use the "turn assert() into assume()" idea for release builds. I

Re: Battle-plan for CTFE

2016-10-16 Thread Uplink_Coder via Digitalmars-d-announce
On Sunday, 16 October 2016 at 10:58:57 UTC, Dmitry Olshansky wrote: That LLVM thing is surely nice to have but I highly doubt it will be allowed as dependency for DMD. --- Dmitry Olshansky LLVM is purely optional. A pure D interpreter exists. LLVM optimises most ctfe btw and returns

Re: Reducing the cost of autodecoding

2016-10-16 Thread Uplink_Coder via Digitalmars-d
On Saturday, 15 October 2016 at 19:07:50 UTC, Patrick Schluter wrote: At least with that lookup table below, you can detect isolated continuation bytes (192 and 193) and invalid codes (above 244). __gshared static immutable ubyte[] charWidthTab = [ 1, 1, 2, 2, 2, 2, 2, 2, 2, 2, 2,

Re: Reducing the cost of autodecoding

2016-10-16 Thread Uplink_Coder via Digitalmars-d
It can also be written like this producing smaller code. But it the cost of slower decoding. dchar myFront(ref char[] str) pure { dchar c = cast(dchar) str.ptr[0]; if (c & 128) { if (c & 64) { int idx = 0; int l = charWidthTab.ptr[c - 192];

Re: Bug in header file generation

2016-10-16 Thread Uplink_Coder via Digitalmars-d
On Saturday, 15 October 2016 at 06:51:44 UTC, Satoshi wrote: Hello, can someone look at this quite simple bug in dmd please? https://issues.dlang.org/show_bug.cgi?id=16590 I cannot release non-opensource libraries without this. You mean auto ref right ? please attach a small test-case. You