1. 01 Apr, 2025 1 commit
  2. 28 Feb, 2025 1 commit
  3. 20 Feb, 2025 1 commit
    • xuxzh1's avatar
      opt1 · 09a693cf
      xuxzh1 authored
      09a693cf
  4. 04 Feb, 2025 1 commit
  5. 08 Jan, 2025 1 commit
  6. 14 Dec, 2024 1 commit
  7. 11 Dec, 2024 1 commit
  8. 10 Dec, 2024 3 commits
    • Daniel Hiltgen's avatar
      Remove unused runner CpuFeatures (#8032) · b9ccb374
      Daniel Hiltgen authored
      The final implementation of #7499 removed dynamic vector requirements
      in favor of a simpler filename based model, and this was left over logic that
      is no longer needed.
      b9ccb374
    • Daniel Hiltgen's avatar
      build: fix typo in override variable (#8031) · 82a02e18
      Daniel Hiltgen authored
      The "F" was missing.
      82a02e18
    • Daniel Hiltgen's avatar
      build: Make target improvements (#7499) · 4879a234
      Daniel Hiltgen authored
      * llama: wire up builtin runner
      
      This adds a new entrypoint into the ollama CLI to run the cgo built runner.
      On Mac arm64, this will have GPU support, but on all other platforms it will
      be the lowest common denominator CPU build.  After we fully transition
      to the new Go runners more tech-debt can be removed and we can stop building
      the "default" runner via make and rely on the builtin always.
      
      * build: Make target improvements
      
      Add a few new targets and help for building locally.
      This also adjusts the runner lookup to favor local builds, then
      runners relative to the executable, and finally payloads.
      
      * Support customized CPU flags for runners
      
      This implements a simplified custom CPU flags pattern for the runners.
      When built without overrides, the runner name contains the vector flag
      we check for (AVX) to ensure we don't try to run on unsupported systems
      and crash.  If the user builds a customized set, we omit the naming
      scheme and don't check for compatibility.  This avoids checking
      requirements at runtime, so that logic has been removed as well.  This
      can be used to build GPU runners with no vector flags, or CPU/GPU
      runners with additional flags (e.g. AVX512) enabled.
      
      * Use relative paths
      
      If the user checks out the repo in a path that contains spaces, make gets
      really confused so use relative paths for everything in-repo to avoid breakage.
      
      * Remove payloads from main binary
      
      * install: clean up prior libraries
      
      This removes support for v0.3.6 and older versions (before the tar bundle)
      and ensures we clean up prior libraries before extracting the bundle(s).
      Without this change, runners and dependent libraries could leak when we
      update and lead to subtle runtime errors.
      4879a234