CI: 03/18/25 upstream sync #294
Merged
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
…ighted sampling without replacement in `jax.random.choice`
This is an exact port of the current Python implementation to C++ for speed. I am being careful not to change the topological order we return in any way in this change, although we may do so in a future change. PiperOrigin-RevId: 737014989
PiperOrigin-RevId: 737040381
PiperOrigin-RevId: 737047069
PiperOrigin-RevId: 737051146
http://github.com/openxla/xla/commit/f52d5e03ce1cf26142a234087dc1d6c3fd919b6f. PiperOrigin-RevId: 737143950
There's no reason why not two custom vmappable types cannot share the same spec_type. However, spec_types was a set, which can cause bugs / exceptions. Suppose that I register two vmappable data_types sharing the same spec_type, and then unregister one of the two. Then, the spec_type is no longer in the set to support the second data_type. Also, an exception will be raised if I try to unregister the two vmappable types (the second call to spec_types.remove). When unregistering a data type, instead of removing its spec_type from the set, we regenerate the set from the remaining vmappable types. PiperOrigin-RevId: 737280270
http://github.com/openxla/xla/commit/936a727db7cefa30027b727b7056b1b5c6064145. PiperOrigin-RevId: 737338103
PiperOrigin-RevId: 737338493
…-bit upcast PiperOrigin-RevId: 737542885
This lets us save on 2 ALU instructions (3x select becomes 1x prmt). PiperOrigin-RevId: 737550598
PiperOrigin-RevId: 737578598
http://github.com/openxla/xla/commit/fcf97e619e26fcb19cffa060df2d0246f6a7ece7. PiperOrigin-RevId: 737581187
These docstrings do not make the tests any more clear and typically just duplicate the test module name. PiperOrigin-RevId: 737611977
…o vector length We can now perform the conversion in groups of 2, 4 or even 8 elements at a time. PiperOrigin-RevId: 737626600
PiperOrigin-RevId: 737632771
…erformance PiperOrigin-RevId: 737665351
…store}`. PiperOrigin-RevId: 737703568
This no longer appears to be used. PiperOrigin-RevId: 737715578
PiperOrigin-RevId: 737720590
Small cleanup, no functional changes intended. PiperOrigin-RevId: 737727727
PiperOrigin-RevId: 737727935
PiperOrigin-RevId: 737733904
This reduces the chances of overflowing a 32-bit integer when computing tile indices. Add unit test to reproduce the overflow with the previous implementation of `blocked_fold_in`. PiperOrigin-RevId: 737778853
The mesh is necessary to add support for clusters to the Mosaic GPU backend. PiperOrigin-RevId: 737792129
PiperOrigin-RevId: 737797815
…AndLoad()`. This is to prepare for updating `PjRtClient::Compile()` to return an unloaded executable [1/N] PiperOrigin-RevId: 737805623
…ounding context PiperOrigin-RevId: 737812111
XLA:GPU recently changed its endianness to little endian to better match LLVM and the rest of the CUDA ecosystem, so we can lift the earlier restrictions. PiperOrigin-RevId: 737934373
With default flushing, it is possible for events to be missed. We should only unsubscribe after we are finished with cupti. PiperOrigin-RevId: 737939327
…MA friendly layouts PiperOrigin-RevId: 737956598
PiperOrigin-RevId: 737957778
http://github.com/openxla/xla/commit/3bb765472122548cc227b8bd2990f00bd533f438. PiperOrigin-RevId: 737959582
This allows us to significantly simplify the generated PTX/SASS, which is currently cluttered with LLVM trying to align slices to start at bit 0 and failing to CSE the right shifts. PiperOrigin-RevId: 737967890
Unswizzled MMAs don't lower correctly, and are not currently intended to be supported. PiperOrigin-RevId: 737981373
charleshofer
approved these changes
Mar 18, 2025
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