Skip to content

Improve device-resident on-device API semantics - #5

Merged
Efithor merged 1 commit into
mainfrom
feat/device-resident-ondevice-api
Mar 2, 2026
Merged

Improve device-resident on-device API semantics#5
Efithor merged 1 commit into
mainfrom
feat/device-resident-ondevice-api

Conversation

@Efithor

@Efithor Efithor commented Mar 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • update matmul on-device behavior to support device-resident JAX inputs cleanly, including fused FP64 return on-device
  • enforce consistent input family requirements (both numpy or both JAX) and reject mixed input types with a clear error
  • normalize on-device output type to match input family for predictable API behavior
  • extend CPU validation checks to cover JAX-input on-device paths and mixed-type rejection
  • add benchmarks/tpu_devres_bench.py for TPU device-resident API benchmarking

Validation notes

CPU workflow coverage now includes:

  • JAX-input fused/ondevice/host accumulation paths
  • output type assertions for JAX inputs
  • mixed input-type rejection behavior

Notes

  • fused on-device mode still requires jax_enable_x64=True
  • this PR focuses on API semantics and transfer behavior; TPU perf validation remains benchmark-driven

Made with Cursor

This keeps JAX inputs device-resident through fused execution, enforces consistent input typing, and extends CPU smoke checks to validate JAX-input behavior and mixed-type rejection.

Made-with: Cursor
@Efithor
Efithor merged commit e3c79f1 into main Mar 2, 2026
1 check passed
@Efithor
Efithor deleted the feat/device-resident-ondevice-api branch March 2, 2026 03:12
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.

1 participant