Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-34971

Vector search fails to compile on x86_32

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Fixed
    • 11.7.0
    • 11.7.1
    • Vector search
    • None

    Description

      In file included from /home/buildbot/x86-debian-12/build/sql/vector_mhnsw.cc:25:
      		 
      /home/buildbot/x86-debian-12/build/sql/bloom_filters.h: In member function ‘void PatternedSimdBloomFilter<T>::Insert(const T**)’:
      		 
      /home/buildbot/x86-debian-12/build/sql/bloom_filters.h:128:23: error: there are no arguments to ‘_mm256_extract_epi64’ that depend on a template parameter, so a declaration of ‘_mm256_extract_epi64’ must be available [-fpermissive]
      		 
        128 |     uint64_t block0 = _mm256_extract_epi64(vecBlockIdxA, 0);

      Attachments

        Issue Links

          is caused by

          New Feature - A new feature of the product, which has yet to be developed. MDEV-34939 vector search in 11.7

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed

          Activity

            Transition Time In Source Status Execution Times
            Sergei Golubchik made transition -
            Open In Progress
            		3d 14h 27m 1
            Sergei Golubchik made transition -
            In Progress Stalled
            		2s 1
            Sergei Golubchik made transition -
            Stalled In Testing
            		1m 14s 1
            Sergei Golubchik made transition -
            In Testing Closed
            		43d 23h 19m 1

            People

              serg Sergei Golubchik
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.