[PATCH] D130869: [AMDGPU] Add GCNMaxILPSchedStrategy
Jay Foad via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Mon Aug 1 09:24:15 PDT 2022
foad added a comment.
Is scheduling for maximum ILP the same thing as scheduling for minimum latency?
Does this patch have anything in common with lib/Target/AMDGPU/GCNILPSched.cpp? (Is that even maintained?)
================
Comment at: llvm/test/CodeGen/AMDGPU/schedule-regpressure-limit.ll:2
; RUN: llc -enable-amdgpu-aa=0 -march=amdgcn -mcpu=tonga -verify-machineinstrs < %s | FileCheck %s
-; RUN: llc -enable-amdgpu-aa=0 -march=amdgcn -mcpu=tonga -misched=gcn-minreg -verify-machineinstrs < %s | FileCheck %s
-; RUN: llc -enable-amdgpu-aa=0 -march=amdgcn -mcpu=tonga -misched=gcn-max-occupancy-experimental -verify-machineinstrs < %s | FileCheck %s
+; RUN: llc -enable-amdgpu-aa=0 -march=amdgcn -mcpu=tonga -misched=gcn-iterative-minreg -verify-machineinstrs < %s | FileCheck %s
+; RUN: llc -enable-amdgpu-aa=0 -march=amdgcn -mcpu=tonga -misched=gcn-iterative-max-occupancy-experimental -verify-machineinstrs < %s | FileCheck %s
----------------
kerbowa wrote:
> foad wrote:
> > Why has this changed?
> I renamed the iterative scheduler cl flags to have this "iterative" prefix. Mostly for clarity and to avoid confusion with this scheduling strategy that is being added in this patch.
Oh I see. I somehow missed that change in AMDGPUTargetMachine.cpp.
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D130869/new/
https://reviews.llvm.org/D130869
More information about the llvm-commits
mailing list