Bernhard Manfred Gruber

Include vcpkg patch

1

vcpkg contains the following patch when building/installing Vc: ```patch diff --git a/cmake/VcConfig.cmake.in b/cmake/VcConfig.cmake.in index 36de476..5cb0e5b 100644 --- a/cmake/VcConfig.cmake.in +++ b/cmake/VcConfig.cmake.in @@ -4,7 +4,7 @@ set_and_check(@PROJECT_NAME@_INSTALL_DIR @PACKAGE_CMAKE_INSTALL_PREFIX@) set_and_check(@PROJECT_NAME@_INCLUDE_DIR @PACKAGE_CMAKE_INSTALL_PREFIX@/include) set_and_check(@PROJECT_NAME@_LIB_DIR @PACKAGE_CMAKE_INSTALL_PREFIX@/lib@LIB_SUFFIX@)...

Add VS2022 to CI

1

This PR adds Visual Studio 2022 to the CI.

WIP

With changes in PR: https://github.com/VcDevel/Vc/pull/292 ## Testcase ```cpp int main() { using V = Vc::native_simd; Vc::Memory m1, m2; m1.setZero(); m2.setZero(); m1 += 1; return m1 != m2; } ``` ##...

Vc version / revision | Operating System | Compiler & Version | Compiler Flags | Assembler & Version | CPU ----------------------|------------------|--------------------|----------------|---------------------|---- branch 1.4 (45fbb882) | Ubuntu 21.10 | g++ 11.2...

Unify the diverging implementation of creating an `__m256i` with all bits set. We currently have diverging implementations for ICC/MSVC and other compilers. See: _Originally posted by @amadio in https://github.com/VcDevel/Vc/pull/286#discussion_r700130444_

[RFC] Mark CATCH cmake variables as advanced

2

I just noticed that we got a lot of cmake variables from Catch2 in the default view of `ccmake`:  Since I don't think that we should tamper with these...