Summary
Update third_party/xpu.txt to pick up the kernel fix from ) which corrects HardtanhBackwardFunctor to use opmath_t
instead of scalar_t for boundary value storage.
Root Cause
The XPU HardtanhBackwardFunctor stored min_val_/max_val_ as scalar_t (bf16),
truncating the caller's correctly-computed fp32 values. E.g., float 0.7 → bf16 0.69921875.
The eager kernel used wrong bounds, while the inductor-decompiled path computed correct bounds
from constant folding. This caused eager vs. inductor numerical disagreement.
Fix (in torch-xpu-ops)
Changed HardtanhBackwardFunctor to store min_val_/max_val_ as opmath_t (fp32)
instead of scalar_t, preserving full precision of boundary values.
See: — issue tracking the hardtanh_backward XPU numerical discrepancy
Pull Request resolved: , https://github.com/EikanWang
Community-Analysen & Experten-Meinungen 0
Verwandte Story-Cluster & Quellen (Vektor-KI)
Ähnliche Beiträge
Auch interessante Nachrichten trunk/25b4b9d3abccb22d469499fe09ddb0a7f1a67147: [xpu] Update xpu.txt pin for hardtanh_backward XPU opmath fix (#186327)
Thematisch verwandte Begriffe: trunk25b4b9d3abccb22d469499fe09ddb0a7f1a67147, Update, xputxt, hardtanhbackward · 6 Treffer
Detecting and responding to Dirty Pipe with Elastic
Videos werden geladen ...
Beiträge werden geladen ...
Videos werden geladen ...
Beiträge werden geladen ...
Videos werden geladen ...
Beiträge werden geladen ...
Videos werden geladen ...
Beiträge werden geladen ...
Videos werden geladen ...
SOCIAL SHARE CARD GENERATOR