pytorch - 💡(How to fix) Fix [Inductor] Forward output mismatch between Eager and Inductor for F.softshrink with bfloat16 and float scalar

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

Error Message

Error logs

Code Example

(torch-nightly) xyt19@Oasis:/tmp$ python bug.py
Eager     : -0.0625
Inductor  : -0.072265625

 Bug

---

import torch
import torch.nn.functional as F

def test_softshrink_mismatch():
    x = torch.tensor([-10.0625], dtype=torch.bfloat16, device="cuda")
    lambd = 9.99  

    def fn(x):
        return F.softshrink(x, lambd)

    eager_out = fn(x)
    
    fn_opt = torch.compile(fn, backend="inductor")
    inductor_out = fn_opt(x)

    print("Eager     :", eager_out.item())       
    print("Inductor  :", inductor_out.item())    
    
    if not torch.allclose(eager_out, inductor_out):
        print("\n Bug")
    else:
        print("\n PASS")

if __name__ == "__main__":
    test_softshrink_mismatch()
RAW_BUFFERClick to expand / collapse

🐛 Describe the bug

When applying torch.nn.functional.softshrink on a bfloat16 CUDA tensor with a float scalar lambd, the output of torch.compile(backend="inductor") does not match the output of Eager mode.

Based on the numerical results, Eager mode appears to cast the scalar lambd (e.g., 9.99) to bfloat16 (10.0) before the computation, yielding -10.0625 + 10.0 = -0.0625. However, Inductor yields -0.072265625, indicating a discrepancy in how the scalar type casting or precision is handled during the kernel execution.

This appears related to #185470, but it is not the same reproducer: #185470 reports F.threshold and says softshrink is fixed, while this reproducer shows F.softshrink itself still mismatches eager for the arithmetic result.

Error logs

(torch-nightly) xyt19@Oasis:/tmp$ python bug.py
Eager     : -0.0625
Inductor  : -0.072265625

 Bug

Minified repro

import torch
import torch.nn.functional as F

def test_softshrink_mismatch():
    x = torch.tensor([-10.0625], dtype=torch.bfloat16, device="cuda")
    lambd = 9.99  

    def fn(x):
        return F.softshrink(x, lambd)

    eager_out = fn(x)
    
    fn_opt = torch.compile(fn, backend="inductor")
    inductor_out = fn_opt(x)

    print("Eager     :", eager_out.item())       
    print("Inductor  :", inductor_out.item())    
    
    if not torch.allclose(eager_out, inductor_out):
        print("\n Bug")
    else:
        print("\n PASS")

if __name__ == "__main__":
    test_softshrink_mismatch()

Expected behavior

The forward output of torch.compile (Inductor) should strictly match the output of Eager mode.

Versions

PyTorch version: 2.13.0.dev20260521+cu130 Is debug build: False CUDA used to build PyTorch: 13.0 ROCM used to build PyTorch: N/A

OS: Ubuntu 24.04.4 LTS (x86_64) GCC version: (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0 Clang version: 18.1.3 (1ubuntu1) CMake version: version 3.28.3 Libc version: glibc-2.39

Python version: 3.10.20 (main, Mar 11 2026, 17:46:40) [GCC 14.3.0] (64-bit runtime) Python platform: Linux-5.15.167.4-microsoft-standard-WSL2-x86_64-with-glibc2.39 Is CUDA available: True CUDA runtime version: 12.0.140 Nvidia driver version: 596.49 cuDNN version: Probably one of the following: /usr/lib/x86_64-linux-gnu/libcudnn.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_adv.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_cnn.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_engines_precompiled.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_engines_runtime_compiled.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_engines_tensor_ir.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_graph.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_heuristic.so.9.21.1 /usr/lib/x86_64-linux-gnu/libcudnn_ops.so.9.21.1 Is XPU available: False HIP runtime version: N/A MIOpen runtime version: N/A Is XNNPACK available: True Caching allocator config: N/A ersions of relevant libraries: [pip3] numpy==2.2.6 [pip3] nvidia-cublas==13.1.1.3 [pip3] nvidia-cuda-cupti==13.0.85 [pip3] nvidia-cuda-nvrtc==13.0.88 [pip3] nvidia-cuda-runtime==13.0.96 [pip3] nvidia-cudnn-cu13==9.20.0.48 [pip3] nvidia-cufft==12.0.0.61 [pip3] nvidia-curand==10.4.0.35 [pip3] nvidia-cusolver==12.0.4.66 [pip3] nvidia-cusparse==12.6.3.3 [pip3] nvidia-cusparselt-cu13==0.8.1 [pip3] nvidia-nccl-cu13==2.29.7 [pip3] nvidia-nvjitlink==13.0.88 [pip3] nvidia-nvtx==13.0.85 [pip3] torch==2.13.0.dev20260521+cu130 [pip3] torchaudio==2.11.0.dev20260525+cu130 [pip3] torchvision==0.28.0.dev20260525+cu130 [pip3] triton==3.7.0+git88b227e2 [conda] numpy 2.2.6 pypi_0 pypi [conda] nvidia-cublas 13.1.1.3 pypi_0 pypi [conda] nvidia-cuda-cupti 13.0.85 pypi_0 pypi [conda] nvidia-cuda-nvrtc 13.0.88 pypi_0 pypi [conda] nvidia-cuda-runtime 13.0.96 pypi_0 pypi [conda] nvidia-cudnn-cu13 9.20.0.48 pypi_0 pypi [conda] nvidia-cufft 12.0.0.61 pypi_0 pypi [conda] nvidia-curand 10.4.0.35 pypi_0 pypi [conda] nvidia-cusolver 12.0.4.66 pypi_0 pypi [conda] nvidia-cusparse 12.6.3.3 pypi_0 pypi [conda] nvidia-cusparselt-cu13 0.8.1 pypi_0 pypi [conda] nvidia-nccl-cu13 2.29.7 pypi_0 pypi [conda] nvidia-nvjitlink 13.0.88 pypi_0 pypi [conda] nvidia-nvtx 13.0.85 pypi_0 pypi [conda] torch 2.13.0.dev20260521+cu130 pypi_0 pypi [conda] torchaudio 2.11.0.dev20260525+cu130 pypi_0 pypi [conda] torchvision 0.28.0.dev20260525+cu130 pypi_0 pypi [conda] triton 3.7.0+git88b227e2 pypi_0 pypi

cc @nairbv @mruberry @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @kadeng @muchulee8 @amjames @aakhundov @coconutruben @jataylo

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

The forward output of torch.compile (Inductor) should strictly match the output of Eager mode.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING