docs: add integration plan awareness, progress tracker, update prompts 04/05 Cross-repo integration plan now tracked in /home/user/INTEGRATION_PLAN.md. Updated lance-graph and consumer crate status in prompts 04 and 05. Added PROGRESS.md for per-plateau task tracking. Tracked 2 pre-existing doctest failures in blackboard (crystal_encoder, udf_kernels). https://claude.ai/code/session_01CdqyUTUfjKZuk8YGJzv6LB#23
Conversation
All "must be ported" items are now marked DONE. Test count updated from stale 286 to actual 880. Added HPC module inventory (55 files), backend inventory (6 files), and architecture notes correcting spec vs reality. https://claude.ai/code/session_01CdqyUTUfjKZuk8YGJzv6LB
…*.rs The previous session created src/backend/simd_compat.rs without reading rustynum's actual architecture. This moves the SIMD polyfill to match rustynum's real structure: three peer files at src/ root. New files (from rustynum): - src/simd.rs — consumer-facing module, re-exports all types + scalar fallback - src/simd_avx512.rs — 11 AVX-512 types copied from rustynum (types only) - src/simd_avx2.rs — AVX2 functions copied from rustynum Kept from simd_compat.rs: - simd_exp_f32, simd_ln_f32 (ndarray additions, now in simd.rs) - scalar fallback for non-x86 (expanded to all 11 types) - All tests What changed: - Import path: crate::backend::simd_compat:: → crate::simd:: - When std::simd stabilizes: crate::simd → std::simd (one word change) - 7 new types added: U8x64, I32x16, I64x8, U32x16, U64x8, F32x8, F64x4 - 9 lowercase aliases: f32x16, f64x8, u8x64, i32x16, i64x8, u32x16, u64x8, f32x8, f64x4 - 890 lib tests pass, 0 failures https://claude.ai/code/session_01CdqyUTUfjKZuk8YGJzv6LB
…s 04/05 Cross-repo integration plan now tracked in /home/user/INTEGRATION_PLAN.md. Updated lance-graph and consumer crate status in prompts 04 and 05. Added PROGRESS.md for per-plateau task tracking. Tracked 2 pre-existing doctest failures in blackboard (crystal_encoder, udf_kernels). https://claude.ai/code/session_01CdqyUTUfjKZuk8YGJzv6LB
c330afc to
fc72dcf
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c330afcdcc
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| pub use crate::simd_avx512::{ | ||
| // 512-bit types | ||
| F32x16, F64x8, U8x64, I32x16, I64x8, U32x16, U64x8, | ||
| // 256-bit AVX2 types | ||
| F32x8, F64x4, |
There was a problem hiding this comment.
Route x86_64 SIMD through the AVX2 backend when AVX-512 is absent
I checked Cargo.toml and there is no avx2 feature, src/lib.rs:236-241 only compiles these modules behind feature = "std", and this re-export still binds every x86_64 build of crate::simd to crate::simd_avx512. That makes the newly added src/simd_avx2.rs unreachable, so AVX2-only hosts still execute the AVX-512 F32x16 path used by hpc::activations/hpc::vml and will continue to fault with SIGILL instead of falling back to the 256-bit implementation.
Useful? React with 👍 / 👎.
| //! AVX-512 SIMD compatibility layer — stable Rust std::arch wrappers. | ||
| //! | ||
| //! Drop-in replacement for `std::simd` portable_simd types. Provides the same | ||
| //! API surface (methods, operators, type names) backed by `std::arch::x86_64` | ||
| //! intrinsics. All intrinsics used here are stable on Rust 1.89+. |
There was a problem hiding this comment.
Preserve the advertised Rust 1.64 MSRV
Cargo.toml still declares rust-version = "1.64", but this new module explicitly depends on intrinsics that are only stable on Rust 1.89+ / 1.93. Because std is a default feature and src/lib.rs now includes this file on every x86_64 build, downstream users and CI jobs pinned to the crate’s documented MSRV will stop compiling on the default target as soon as they pick up this commit.
Useful? React with 👍 / 👎.
No description provided.