forked from jax-ml/jax
-
Notifications
You must be signed in to change notification settings - Fork 5
CI: 06/06/25 upstream sync #460
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PiperOrigin-RevId: 762475094
PiperOrigin-RevId: 762490961
Also fix accumulator argument when it's dynamic. PiperOrigin-RevId: 762509416
Creating smaller build rules enforces better organized dependency graphs in the JAX project, helps pytype propagate annotations correctly, and leads to improved build and iteration times. This was unblocked by moving batching & ad to their own rules in prior changes. PiperOrigin-RevId: 762527517
…ailure. PiperOrigin-RevId: 762546985
…te a refactor. PiperOrigin-RevId: 762547026
PiperOrigin-RevId: 762562570
PiperOrigin-RevId: 762567722
…e of kv cache is a scalar float value) PiperOrigin-RevId: 762576286
Creating smaller build rules enforces better organized dependency graphs in the JAX project, helps pytype propagate annotations correctly, and leads to improved build and iteration times. PiperOrigin-RevId: 762589488
add marin to ecosystem
Creating smaller build rules enforces better organized dependency graphs in the JAX project, helps pytype propagate annotations correctly, discourages private imports downstream, and leads to improved build and iteration times. PiperOrigin-RevId: 762621491
PiperOrigin-RevId: 762621608
PiperOrigin-RevId: 762623893
Move the logic verifying that `shape_assertion` custom calls have side effects to run before MLIR optimizations are applied instead of after. Any `shape_assertion` custom call violating this condition (i.e. declared as pure) is likely to be removed by dead-code elimination, making it undetectable after optimizations. (Until recently, the test passed because DCE wasn't correctly applied to `custom_call` ops.) PiperOrigin-RevId: 762634648
PiperOrigin-RevId: 762956847
…tributed tests I added them in all other files, but forgot about this one. PiperOrigin-RevId: 763352483
…ive matmul PiperOrigin-RevId: 763353415
The C128 matmuls will be routed to cuBLAS rather than to be handled by the loop emitter, causing a very slight numerical difference. Therefore, don't be very strict in the comparison. PiperOrigin-RevId: 763397887
PiperOrigin-RevId: 763697379
…om-ptxas-and-llvm PiperOrigin-RevId: 763701410
…yout in some ops I can't explain it, but if we don't do it then the verifier sometimes fails... I'm not even sure how to properly trigger this in a test right now, but worst case it would result in more verifier failures to fix, so I think it's fine to merge as is. PiperOrigin-RevId: 763711454
`TCGEN05_COL` is to `TCGEN05` what `WGMMA_ROW` is to `WGMMA`. PiperOrigin-RevId: 767500979
PiperOrigin-RevId: 767596548
PiperOrigin-RevId: 767610707
The distinction between collective/non-collective TMEM is done at allocation time so we need to allocate two separate blocks. PiperOrigin-RevId: 767611353
PiperOrigin-RevId: 767611487
…d there's no need to do the same calculation if the keys don't change. PiperOrigin-RevId: 767612102
This leads to a better dependency graph and avoids local imports.
PiperOrigin-RevId: 767687785
Co-authored-by: Dougal Maclaurin <[email protected]>
…not-supported-on-gpu PiperOrigin-RevId: 767693519
PiperOrigin-RevId: 767694982
…TPU/GPU arrays raise a helpful error and don't take the new experimental cross-host device transfer path. PiperOrigin-RevId: 767696126
PiperOrigin-RevId: 767702568
PiperOrigin-RevId: 767751945
PiperOrigin-RevId: 767755766
I messed up the first time, the output register is naturally 16-bit wide. The PTX looks much cleaner now. PiperOrigin-RevId: 767756118
PiperOrigin-RevId: 767767487
…/COL layouts. PiperOrigin-RevId: 767772068
PiperOrigin-RevId: 767827963
PiperOrigin-RevId: 767902551
…pose, and canonicalization for where it cannot. To support Transpose of int8 we need to extend to i32, run transpose with bf16 and truncate. PiperOrigin-RevId: 767915759
PiperOrigin-RevId: 767920329
…he (unsupported) TPU PjRt C API client also contains the string "TFRT TPU". PiperOrigin-RevId: 767921346
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Daily sync with upstream