Re: intel-intrinsics v1.0.0
On Wednesday, 13 February 2019 at 19:55:05 UTC, Guillaume Piolat wrote: On Wednesday, 13 February 2019 at 04:57:29 UTC, Crayo List wrote: On Wednesday, 6 February 2019 at 01:05:29 UTC, Guillaume Piolat wrote: "intel-intrinsics" is a DUB package for people interested in x86 performance that want neither to write assembly, nor a LDC-specific snippet... and still have fastest possible code. This is really cool and I appreciate your efforts! However (for those who are unaware) there is an alternative way that is (arguably) better; https://ispc.github.io/index.html You can write portable vectorized code that can be trivially invoked from D. ispc is another compiler in your build, and you'd write in another language, so it's not really the same thing. That's mostly what I said, except that I did not say it's the same thing. It's an alternative way to produce vectorized code in a deterministic and portable way. This is NOT an auto-vectorizing compiler! I haven't used it (nor do I know anyone who do) so don't really know why it would be any better 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. I highly recommend browsing through the walkthrough example; https://ispc.github.io/example.html For example, I have code that I can run on my Xeon Phi 7250 Knights Landing CPU by compiling with --target=avx512knl-i32x16, then I can run the exact same code with no change at all on my i7-5820k by compiling with --target=avx2-i32x8. Each time I get optimal code. This is not something you can easily do with intrinsics!
Re: intel-intrinsics v1.0.0
On Wednesday, 13 February 2019 at 04:57:29 UTC, Crayo List wrote: On Wednesday, 6 February 2019 at 01:05:29 UTC, Guillaume Piolat wrote: "intel-intrinsics" is a DUB package for people interested in x86 performance that want neither to write assembly, nor a LDC-specific snippet... and still have fastest possible code. This is really cool and I appreciate your efforts! However (for those who are unaware) there is an alternative way that is (arguably) better; https://ispc.github.io/index.html You can write portable vectorized code that can be trivially invoked from D. ispc is another compiler in your build, and you'd write in another language, so it's not really the same thing. I haven't used it (nor do I know anyone who do) so don't really know why it would be any better
Re: DCD 0.11.0 released
On Tuesday, 12 February 2019 at 19:48:25 UTC, Seb wrote: On Tuesday, 12 February 2019 at 19:46:29 UTC, notna wrote: On Tuesday, 12 February 2019 at 17:55:46 UTC, Basile B. wrote: On Monday, 11 February 2019 at 20:40:32 UTC, notna wrote: Installing DCD Downloading from https://github.com/dlang-community/DCD/releases/download/v0.10.2/dcd-v0.10.2-windows-x86.zip to C:\Users\\AppData\Roaming\code-d\bin Failed installing: std.net.curl.CurlException@std\net\curl.d(4340): Peer certificate cannot be authenticated with given CA certificates on handle I don't know what you are talking about, how are you installing DCD ? What is the installer you talk about ? Also the version number of this release is 0.11.0, not 0.10.2 Thats the errors vscode, better code-d, shows... seems like you want to update dcd and use the curl lib for that, which throws an error because the download (GitHub?) certificate cannot be validated. Just check the news group (or the "forum") for this code-d error and you should find a couple of similar complains. Have your ever considered reporting it at the code-d repository? https://github.com/Pure-D/code-d/issues It should drastically increase the chances of the maintainers of code-d actually seeing your problems. Honestly, it would be nice if dub would collaborate with D in terms of issues so possibly people could report issues with packages at https://issues.dlang.org/
