[all-commits] [llvm/llvm-project] 9ae693: AMDGPU: Check for subreg match when folding throug...
Matt Arsenault via All-commits
all-commits at lists.llvm.org
Mon May 19 10:26:54 PDT 2025
Branch: refs/heads/users/arsenm/issue139908/check-reg-sequence-splat-use-operand-type
Home: https://github.com/llvm/llvm-project
Commit: 9ae69332688f4864b25449a694dc67968a1bf45b
https://github.com/llvm/llvm-project/commit/9ae69332688f4864b25449a694dc67968a1bf45b
Author: Matt Arsenault <Matthew.Arsenault at amd.com>
Date: 2025-05-19 (Mon, 19 May 2025)
Changed paths:
M llvm/lib/Target/AMDGPU/SIFoldOperands.cpp
M llvm/test/CodeGen/AMDGPU/constrained-shift.ll
M llvm/test/CodeGen/AMDGPU/global-saddr-load.ll
M llvm/test/CodeGen/AMDGPU/llvm.amdgcn.mfma.gfx90a.ll
M llvm/test/CodeGen/AMDGPU/operand-folding.ll
M llvm/test/CodeGen/AMDGPU/packed-fp32.ll
M llvm/test/CodeGen/AMDGPU/si-fold-operands-subreg-imm.mir
Log Message:
-----------
AMDGPU: Check for subreg match when folding through reg_sequence
We need to consider the use instruction's intepretation of the bits,
not the defined immediate without use context. This will regress
some cases where we previously coud match f64 inline constants. We
can restore them by either using pseudo instructions to materialize f64
constants, or recognizing reg_sequence decomposed into 32-bit pieces for them
(which essentially means recognizing every other input is a 0).
Fixes #139908
To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications
More information about the All-commits
mailing list