Skip to content

[pull] master from tensorflow:master#1682

Merged
pull[bot] merged 5 commits into
GesuBackups:masterfrom
tensorflow:master
Apr 1, 2026
Merged

[pull] master from tensorflow:master#1682
pull[bot] merged 5 commits into
GesuBackups:masterfrom
tensorflow:master

Conversation

@pull

@pull pull Bot commented Apr 1, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

tensorflower-gardener and others added 5 commits March 31, 2026 21:12
PiperOrigin-RevId: 892693575
PiperOrigin-RevId: 892695144
It is not needed.

PiperOrigin-RevId: 892731368
It looks like it was run by mistake on all platforms, although it should serve
as regression test for a PTXAS bug (so relevant to GPU backend only). By now,
the bug is long fixed and we don't need this test anymore.

PiperOrigin-RevId: 892746106
GpuTargetConfig has a constructor that takes a `StreamExecutor`
and determines the config from the current GPU. In this process
an instance of `DeviceDescription` is being stored in the `GpuTargetConfig`. This instance contains fields that are unique to the current GPU - like the PCI Bus ID and some unique NVLINK UUIDs.

That makes the GpuTargetConfig between 2 GPUs of the same model not identical anymore which is a problem when used as a cache key like in a lot of our systems.

This change removes the device specific fields from `DeviceDescription` when constructing a `GpuTargetConfig`. We shouldn't depend on those fields when targeting a GPU anyway. In fact I have checked, none of these fields are being used in the XLA compilation process. The only usages are in Tensorflow (no `GpuTargetConfig`, just bare `DeviceDescription` which is fine), and in `CudaExecutor` which is runtime and also okay.

PiperOrigin-RevId: 892760770
@pull pull Bot locked and limited conversation to collaborators Apr 1, 2026
@pull pull Bot added the ⤵️ pull label Apr 1, 2026
@pull pull Bot merged commit 19f1489 into GesuBackups:master Apr 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants