Tomasz Kaminski [Tuesday, 28 October 2025, 10:51:23 CET]:
> > * include/bits/vec_ops.h: New file.
> > * include/bits/version.def: Add simd.
> > * include/bits/version.h: Regenerate.
> > * include/std/simd: New file.
>
> The declarations from simd needs to also be exported from std module,
> so libstdc++-v3/src/c++23/std.cc.in needs to be edited to support it.
> But I think we could do that as a separate commit.
I think that was all you wrote in this mail, right?
Can you either delete the rest of the quoted mail or somehow mark your last
comment so that I know I can stop looking?
RFC:
I have started to copy my tests over into testsuite/26_numerics/simd. But as
with std::experimental::simd, I don't know where to stop. A thorough test
needs
template for (constexpr int n : _IotaArray<67>) // or more
(test<simd::vec<all_vectorizable_types, n>>()...);
but that exceeds any reasonable resource usage by far. It compiles for hours
if you have TBs of memory (I guess — I don't).
And is there a way to specify tests need to run with -march=x86-64,
-march=x86-64-v2, -march=x86-64-v3, … ? I can select one per .cc file and then
include the actual test, right? The proper way is to run with a target_list
argument to runtest, but can that be part of the check target?
- Matthias
--
──────────────────────────────────────────────────────────────────────────
Dr. Matthias Kretz https://mattkretz.github.io
GSI Helmholtz Center for Heavy Ion Research https://gsi.de
std::simd
──────────────────────────────────────────────────────────────────────────
