Trouble with PyTorch inductor
14 posts from 11 people10d activeSteady, +1 this week
Posts per day
The posts behind it
[inductor] 'MultiOutput' object has no attribute 'data' when a TemplateBuffer.build_multi_outputs output is returned and also used
### 🐛 Describe the bug `torch.compile` fails in Inductor's lowering when the output of a template kernel built with `TemplateBuffer.build_multi_outputs` is returned from the graph and also has another user. The only caller of `build_multi_outputs` I know of is Helion's Inductor...
[inductor][cpu] C++ compile error for `min`/`max` over a combination of two boolean masks
### 🐛 Describe the bug `min` or `max` over a boolean tensor built from two masks, such as `(x > 0) & (x 0).min()`) compiles, and so do `amin` and `any` over two masks. In the generated kernel, the two masks are cast to `int32` before `&`, so the value is a `VecMask `, while the...
[Inductor] Support ND Tiling
### 🚀 The feature, motivation and pitch # [External version] ND tiling in Inductor # Human summarry This is an extension of the tensor descriptor / tiling work tracked in https://github.com/pytorch/pytorch/issues/125077. This is a condensed version of a larger internal document...
Inductor ignores / doesn't preserve Triton JIT options for helpers
...programs from the same kernel. The generated source and persistent cache keys also fail to distinguish helpers whose compilation-relevant options differ. The related root-kernel path has the same underlying metadata problem: `do_not_specialize` and...
[Inductor] torch.mm and torch.bmm do not respect `out_dtype` when using `native_matmul`
### 🐛 Describe the bug When using `torch._inductor.config.triton.native_matmul = True`, `torch.mm` and `torch.bmm` called with fp16/b16 inputs and `output_dtype=torch.float32`, each return the input dtype rather than fp32. MRE: ### Error logs This is a silent error. ###...
`[Inductor][CPU] torch.var returns NaN for large-magnitude constant float64 inputs while eager returns 0`
### 🐛 Describe the bug On CPU, `torch.var` under `torch.compile(backend="inductor")` returns **NaN** for large-magnitude constant `float64` inputs, while eager returns the correct `0`. The divergence appears once the squared magnitude approaches the **float64** range limit...
[Inductor] torch.mvlgamma silently returns zeros for p=0 instead of raising the eager p>=1 check
### 🐛 Describe the bug `torch.mvlgamma(x, p)` validates `p` in eager (`TORCH_CHECK(p >= 1, "p has to be greater than or equal to 1")`, `aten/src/ATen/native/UnaryOps.cpp`), but under `torch.compile` (Inductor) this check is lost: the op decomposes through...
`[Inductor] nll_loss silently computes a loss for a shape-mismatched target that eager and aot_eager reject`
### 🐛 Describe the bug `torch.nn.functional.nll_loss` with a target whose spatial dimensions do not match the input raises a `RuntimeError: size mismatch` in eager **and** under `torch.compile(backend="aot_eager")`, but `backend="inductor"` **silently computes a (meaningless)...
[inductor] AOTI arrayref (stack-allocation) wrapper tests consistently red on trunk since mid-September
...unrelated PRs of mine, and it reproduces on main itself, so here is a tracker. **What is failing** `test/inductor/test_aot_inductor_arrayref.py::AOTInductorTestABICompatibleCpuWithStackAllocation`: 45 distinct tests across the two shards on the latest completed main run I...
[Inductor] soft_margin_loss returns wrong dtype for mixed-dtype input and target
### 🐛 Describe the bug `torch.compile` with the Inductor backend produces the wrong output dtype for `F.soft_margin_loss` when the input and target have different floating-point dtypes. Eager and `aot_eager` preserve the input dtype (`float32`), while Inductor promotes the...
[Inductor] Tensor.exponential_() can return +inf
### 🐛 Describe the bug `torch.compile` with the Inductor backend can occasionally make `Tensor.exponential_()` return `+inf` on both CPU and CUDA. PyTorch documents `Tensor.exponential_()` as sampling from an exponential distribution with actual support `(0, inf)`, so `+inf` is...
[inductor][cpu] Compiled "flex_attention" returns wrong values with strided view with storage offset
### 🐛 Describe the bug (On CPU) `torch.compile` of `flex_attention` produces wrong results when q, k and v are slices of projection output and q/k are computed inside the graph. Eager `flex_attention` matches SDPA. Calling `.contiguous()` on v makes the compiled result match...
[inductor][while_loop] carried-input mutation validation is bypassed by auto-functionalization
I re-reviewed the updated PR and reproduced the `cpp_wrapper` failure. The new test makes carried-input mutation depend on an unrelated captured-tensor mutation, contradicting the documented contract. > [AI-assisted analysis] > > ## Bug > > `torch.while_loop` documents that...
[inductor] mix-order reduction: split column sum ignores xmask, wrong results when rows % XBLOCK != 0
With `triton.mix_order_reduction` on (OSS default), a row and a column reduction over the same input fuse into one kernel. The column reduction is accumulated per RSPLIT chunk with `tl.sum(<value, 0)` without masking the tile by `xmask`. Padded rows load `other=0.0`, so any...
Companies and products named
About this problem
Evidence
14 posts from 11 people in 1 place, about 1 a week over 75 days. Mostly on pytorch/pytorch. Tools named alongside: NVIDIA, GitHub, AWS, PyPI.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about PyTorch with no known issue, sharing the word "inductor". First post Sep 3, 2026, latest Nov 16, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other PyTorch problems
Running PyTorch locally hits memory and speed limits
10 posts from 6 people on GitHub issues, Hacker News.
PyTorch writes buggy code that is hard to review
2 posts from 1 person on GitHub issues. Unverified.
PyTorch users keep filing bugs
Top post: "Meta-issue: torch.compile gaps found via the CPython test suite", one of 50 posts from 41 people on GitHub issues, Reddit, Stack Overflow.
PyTorch upgrades break working setups
29 posts from 23 people on GitHub issues, Reddit.
PyTorch GPU access and drivers are painful
17 posts from 17 people on GitHub issues, Reddit.
PyTorch builds are slow or flaky
11 posts from 2 people on GitHub issues.
Trouble with PyTorch true
Top post: "PaddleOCR-VL: position embedding interpolation changed from align_corners=False to True", one of 10 posts from 7 people on GitHub issues.
PyTorch deprecations force unplanned migrations
8 posts from 5 people on GitHub issues.
Trouble with PyTorch input
Top post: "Generation crashes with encoder_repetition_penalty when encoder_outputs are provided without input_ids", one of 7 posts from 7 people on GitHub issues.
Fine-tuning PyTorch is costly and unpredictable
5 posts from 5 people on GitHub issues, Reddit.
Trouble with PyTorch dynamic
Top post: "DISABLED test_weight_norm_1d_and_reduced_dtypes_dynamic_shapes (__main__.DynamicShapes)", one of 5 posts from 3 people on GitHub issues, Reddit.
Trouble with PyTorch windows
Top post: "Bundled cuDNN fails on first use since #202206 when no cuDNN is on PATH (Cannot load symbol cudnnGetVersion)", one of 4 posts from 4 people on GitHub issues.
History