simd
Here are 412 public repositories matching this topic...
我发现examples/retinaface.cpp中,如果开启OMP加速的话似乎在检测到人脸时会发生内存泄漏,但我定位不了这个问题的具体原因。
值得注意的时,如果将qsort_descent_inplace函数中的OMP指令注释掉这个问题就会消失掉。
static void qsort_descent_inplace(std::vector<FaceObject>& faceobjects, int left, int right)
{
int i = left;
int j = right;
float p = faceobjects[(left + right) / 2].prob;
...
// #pragma omp parallel sections
{
// #pragma-
Updated
Jun 25, 2020 - C++
benchdnn help CLI
Just a suggestion to add a "--help" support to benchdnn.
As today benchdnn does nt seem to have a --help support, the doc being only available online on this page:
https://github.com/intel/mkl-dnn/tree/master/tests/benchdnn
the proposal is to add a minimum of "print usage" to the benchdnn CLI tool.
Environ
-
Updated
May 29, 2020 - C++
So many mistakes are made due to the default 'varying' decoration on a type when no decoration is given, that there should be a warning for it - disabled by default to not break current code.
#pragma warning(varying) //to enable
--wvarying // CLI to enable
-
Updated
Apr 14, 2020 - C
Conan package
-
Updated
Jul 2, 2020 - C++
I am sorry but I don't know how to put it into an Issue format, so I have to explain it plainly.
Dear contributors,
It seems that every source file in Vc library has the following copyright notice:
/* This file is part of the Vc library. {{{
Copyright © 2009-2015 XXX <xxx@example.com>
Redistribution and use in source and binary forms, with or without
modification, are permitteThe dynamic dispatch example, as described in documentation seems to work using the Makefile approach.
However, with a CMake file, using the appropriate CMake module, the build fails with error:
main.cpp:(.text+0x5): undefined reference to print_arch()'
-
Updated
Jun 25, 2020 - C++
At least on x86, the fastest intrinsics for shuffling the contents of a vector or blending data from two vectors take an immediate operand, which must be a compile-time constant. So there would be a use case for a compile-time version of xsimd::select(), as it could use these faster instructions.
An example of prior art for this is the shuffle() instruction family in bSIMD:
In the documentation, the sentence A trait representing an affine transformation that can be applied to points or vectors. An affine transformation is one which is cut off. I'm not sure how it's meant to end and don't know enough about what an affine transformation is to fix it, but thought I'd point it out
Docs about dest param :
"You can pass all parameter same (this is similar to m1 *= m1), you can pass dest as m1 or m2 (this is similar to m1 *= m2)" (c)
But some functions behave differently. For example:
vec3 A = {0,0,2};
vec3 B = {2,0,0};
glm_vec3_cross(A, B, A); // A = {0, 4, -8} was expected A = {0, 4, 0}
-
Updated
Sep 21, 2017 - Rust
-
Updated
May 5, 2020 - C#
-
Updated
Jun 18, 2020 - C++
-
Updated
Jul 2, 2020 - C
-
Updated
Jun 7, 2020 - C
Big thanks for making this cool tool open-source.
By any chance, is there a complete list of instructions which are currently not supported / under development please? For instance, I am aware that vgatherdpd does not work.
We should add WASM simd128 implementations of as many SSE/SSE2/etc. functions as possible.
Some of the functions won't see much, if any, improvements since we already have GCC-style vector extension and OpenMP SIMD support. The real benefit will be for the functions that can't use GCC-style vectors. For example, saturated operations, min/max, etc. And of course there will be a lot of cases w
-
Updated
May 29, 2020 - C++
Modifying MXCSR is insta-UB in LLVM, and inspecting it is kind of pointless since LLVM can change it behind your back however it wants (e.g. depending on the opt-level).
We should deprecate these and tell people not to use them, since they won't do what they want them to do.
Users that want to mess with MXCSR, should do so in such a way that doesn't trigger UB in LLVM. For example, by openi
Improve this page
Add a description, image, and links to the simd topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the simd topic, visit your repo's landing page and select "manage topics."


Now when oss-fuzz provides pretty code coverage, it is easy to see which parts of the code are not fuzzed properly.
Identify what can be done, and add fuzzers targeting the uncovered code.