core.simd woes

Simen Kjaeraas simen.kjaras at gmail.com
Tue Oct 9 07:52:08 PDT 2012


On 2012-10-09, 16:20, jerro wrote:

>> An alternative approach is to have one module per architecture or  
>> compiler.
>
> You mean like something like std.simd.x86_gdc? In this case a user would  
> need to write a different version of his code for each compiler or write  
> his own  wrappers (which is basically what we have now). This could  
> cause a lot of redundant work. What is worse, some people wouldn't  
> bother, and then we would have code that only works with one D compiler.

Nope, like:

module std.simd;

version(Linux64) {
     public import std.internal.simd_linux64;
}


Then all std.internal.simd_* modules have the same public interface, and
only the version that fits /your/ platform will be included.

-- 
Simen


More information about the Digitalmars-d mailing list