On Saturday, 28 March 2020 at 18:01:37 UTC, Crayo List wrote:
On Saturday, 28 March 2020 at 06:56:14 UTC, Bruce Carneal wrote:
On Saturday, 28 March 2020 at 05:21:14 UTC, Crayo List wrote:
On Monday, 23 March 2020 at 18:52:16 UTC, Bruce Carneal wrote:
[snip]
Explicit SIMD code, ispc or other,
On Saturday, 28 March 2020 at 06:56:14 UTC, Bruce Carneal wrote:
On Saturday, 28 March 2020 at 05:21:14 UTC, Crayo List wrote:
On Monday, 23 March 2020 at 18:52:16 UTC, Bruce Carneal wrote:
[snip]
(on the downside you have to guard against compiler code-gen
performance regressions)
auto ve
On Saturday, 28 March 2020 at 05:21:14 UTC, Crayo List wrote:
On Monday, 23 March 2020 at 18:52:16 UTC, Bruce Carneal wrote:
[snip]
(on the downside you have to guard against compiler code-gen
performance regressions)
auto vectorization is bad because you never know if your code
will get v
On Monday, 23 March 2020 at 18:52:16 UTC, Bruce Carneal wrote:
When speeds are equivalent, or very close, I usually prefer
auto vectorized code to explicit SIMD/__vector code as it's
easier to read. (on the downside you have to guard against
compiler code-gen performance regressions)
One odd
When speeds are equivalent, or very close, I usually prefer auto
vectorized code to explicit SIMD/__vector code as it's easier to
read. (on the downside you have to guard against compiler
code-gen performance regressions)
One oddity I've noticed is that I sometimes need to use
pragma(inline,
