Skip to content

xsimd: update to 14.2.0.#58127

Merged
Duncaen merged 1 commit into
void-linux:masterfrom
jason1987d:xsimd
May 10, 2026
Merged

xsimd: update to 14.2.0.#58127
Duncaen merged 1 commit into
void-linux:masterfrom
jason1987d:xsimd

Conversation

@jason1987d
Copy link
Copy Markdown
Contributor

@jason1987d jason1987d commented Dec 9, 2025

Testing the changes

  • I tested the changes in this PR: YES

Local build testing

  • I built this PR locally for my native architecture, x86_64-libc

Comment thread srcpkgs/xsimd/template
Comment thread srcpkgs/xsimd/template Outdated
@jason1987d jason1987d changed the title xsimd: update to 14.0.0. xsimd: update to 14.0.0, adopt. Dec 9, 2025
@jason1987d
Copy link
Copy Markdown
Contributor Author

Trying to figure out how to properly patch based on xtensor-stack/xsimd#1246 which is based on master. How to proceed?

@jason1987d jason1987d changed the title xsimd: update to 14.0.0, adopt. xsimd: update to 14.0.0. Feb 11, 2026
@jason1987d jason1987d force-pushed the xsimd branch 2 times, most recently from 7796d8d to 021910d Compare February 11, 2026 03:40
@JkktBkkt
Copy link
Copy Markdown
Contributor

Trying to figure out how to properly patch based on xtensor-stack/xsimd#1246 which is based on master. How to proceed?

Does only applying this commit fix it? xtensor-stack/xsimd@4baba66

The other one is logging changes, which seems to be mostly unrelated / other issue tackled in same PR

Comment thread srcpkgs/xsimd/template Outdated
@jason1987d
Copy link
Copy Markdown
Contributor Author

Trying to figure out how to properly patch based on xtensor-stack/xsimd#1246 which is based on master. How to proceed?

Does only applying this commit fix it? xtensor-stack/xsimd@4baba66

The other one is logging changes, which seems to be mostly unrelated / other issue tackled in same PR

Applied it. The tests there are still failing.

@jason1987d
Copy link
Copy Markdown
Contributor Author

Trying to figure out how to properly patch based on xtensor-stack/xsimd#1246 which is based on master. How to proceed?

Does only applying this commit fix it? xtensor-stack/xsimd@4baba66
The other one is logging changes, which seems to be mostly unrelated / other issue tackled in same PR

Applied it. The tests there are still failing.

Following up on this situation. I was able to get both commits applied as patches, with a slight edit to line numbers in one of the hunks that was getting rejected. See my latest comment on xtensor-stack/xsimd#1244 .

@jason1987d jason1987d changed the title xsimd: update to 14.0.0. xsimd: update to 14.1.0. Mar 21, 2026
@jason1987d jason1987d changed the title xsimd: update to 14.1.0. xsimd: update to 14.2.0. Apr 29, 2026
Comment thread srcpkgs/xsimd/template Outdated
@jason1987d
Copy link
Copy Markdown
Contributor Author

Finally got the test case for x86_64-musl fixed. Applied as a patch here.
xtensor-stack/xsimd#1336

@jason1987d
Copy link
Copy Markdown
Contributor Author

Also, tested and worked with this sample code.

#include <iostream>
#include <xsimd/xsimd.hpp>

// Vector size, adjust it for your testing
const size_t N = 8;

int main() {
    // Create two arrays of size N
    float a[N] = {1.0, 2.0, 3.0, 4.0, 5.0, 6.0, 7.0, 8.0};
    float b[N] = {8.0, 7.0, 6.0, 5.0, 4.0, 3.0, 2.0, 1.0};
    float result[N];

    // Define the SIMD type for float (you can change it based on your architecture)
    using simd_float = xsimd::simd_type<float>;

    // Perform SIMD addition
    for (size_t i = 0; i < N; i += simd_float::size) {
        simd_float vec_a = xsimd::load_aligned(&a[i]);
        simd_float vec_b = xsimd::load_aligned(&b[i]);
        simd_float vec_result = vec_a + vec_b;

        // Store the result
        vec_result.store_aligned(&result[i]);
    }

    // Print out the result
    std::cout << "Result of SIMD addition:" << std::endl;
    for (size_t i = 0; i < N; ++i) {
        std::cout << result[i] << " ";
    }
    std::cout << std::endl;

    return 0;
}

@Duncaen Duncaen merged commit 480b271 into void-linux:master May 10, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants