Alexander Droste
Alexander Droste
+1 This not only concerns visual appearance but also assumes the Rust code is built through Cargo which might not be the case in favor of another build system.
@baconpaul can we build and run the vst3 validator on ci, or is this again a licensing problem? we could otherwise consider running `pluginval` compiled with asan as a 'host'.
Ya, these issues are very similar then.
Will add this to CI once we land a small example clap plugin, as described in: https://github.com/free-audio/clap-wrapper/issues/119.
Closed, as we will push the scan into Rust.
Surprised that we don't really use this anywhere. If we don't have any users that rely on vortex-ffi, sgtm.
@gatesn Do you have a hunch?
Heads up that we can't micro-benchmark avx512 with codspeed, as valgrind/callgrind does not support avx512. Saying you'll get numbers for avx2 if it is implemented: ``` - name: Build benchmarks...
> @0ax1 is there a way for me to disable the benchmark just for codspeed? ~~You shouldn't need to. We compile for AVX2, so the AVX512 version shouldn't be picked...
> Are these regressions expected with a compiler update? Different inlining behavior or the linker change maybe: https://blog.rust-lang.org/2025/09/01/rust-lld-on-1.90.0-stable/