Skip to content

Conversation

@rfsaliev
Copy link
Collaborator

@rfsaliev rfsaliev commented Dec 10, 2025

This change adds SVS distance computation tests to catch memory access error caused by unmasked vector loading instructions

A clear and concise description of what the PR is solving.

Which issues this PR fixes

  1. #...
  2. MOD...

Main objects this PR modified

  1. ...
  2. ...

Mark if applicable

  • This PR introduces API changes
  • This PR introduces serialization changes

meiravgri added a commit that referenced this pull request Dec 10, 2025
* Use system page protection to catch the unmasked vector loading issue
* Do not use pre-compiled SVS binaries but compile from sources
* Update SVS submodule to the latest main with AVX2 fixes
GLIBC_2_26_FOUND)
endif()

cmake_dependent_option(SVS_SHARED_LIB "Use SVS pre-compiled shared library" ON "USE_SVS AND GLIBC_FOUND AND SVS_LVQ_SUPPORTED" OFF)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TODO: revert this change upon SVS binaries update

@rfsaliev rfsaliev force-pushed the rfsaliev/test-svs-distance branch from 79b8abd to 5128cf4 Compare December 11, 2025 12:18
@rfsaliev rfsaliev changed the title Add test with direct call to SVS distance computations [SVS] Add test with direct call to SVS distance computations Dec 11, 2025
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.

2 participants