intel-intrinsics v1.0.0

[Guillaume Piolat]

On Thursday, 14 February 2019 at 21:45:57 UTC, Crayo List wrote:
> On Thursday, 14 February 2019 at 16:13:21 UTC, Ethan wrote:
>> On Wednesday, 13 February 2019 at 23:26:48 UTC, Crayo List 
>> wrote:
>>> And that's precisely why I posted here; for those people that 
>>> have interest in vectorizing their code in a portable way to 
>>> be aware that there is another (arguably) better way.
>>
>> All power to the people that have code that simple. But 
>> auto-vectorising in any capacity is the wrong way to do things 
>> in my field. An intrinsics library is vital to write highly 
>> specialised code.
>>
>> The tl;dr here is that we *FINALLY* have a minimum-spec for 
>> x64 CPUs represented with SSE intrinsics. Instead of whatever 
>> core.simd is. That's really important, and talks about 
>> auto-vectorisation are really best saved for another thread.
>
> Please re-read my post carefully!

I think ispc is interesting, and a very D-ish thing to have would 
be an ispc-like compiler at CTFE that outputs LLVM IR (or 
assembly or intel-intrinsics). That would break the language 
boundary and allows inlining. Though probably we need newCTFE for 
this, as everything interesting seems to need newCTFE :) And it's 
a gigantic amount of work.