[PATCH] D53055: [MCA] Constrain the number of bytes fetched per cycle.
Owen Rodley via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Tue Oct 9 17:08:04 PDT 2018
orodley created this revision.
Herald added subscribers: llvm-commits, gbedwell.
Herald added a reviewer: andreadb.
For an example of this, see the Intel Optimization Reference Manual,
2.5.2.2 ("Instruction Fetch Unit"):
An instruction fetch is a 16-byte aligned lookup through the ITLB into
the instruction cache and instruction prefetch buffers. A hit in the
instruction cache causes 16 bytes to be delivered to the instruction
predecoder.
The model here (fetching exactly 16 bytes every cycle) is incomplete, as
it assumes every instruction is aligned and in icache, but it's an
improvement.
This is usually not a bottleneck, as stalls elsewhere will hide it, but
it can make a difference in some cases. Further work would be to
classify these cases in the report output - if there are unutilised
issue slots while there is no backend stall, we are frontend bound.
Repository:
rL LLVM
https://reviews.llvm.org/D53055
Files:
llvm/tools/llvm-mca/include/Context.h
llvm/tools/llvm-mca/include/Stages/FetchStage.h
llvm/tools/llvm-mca/lib/Context.cpp
llvm/tools/llvm-mca/lib/Stages/FetchStage.cpp
llvm/tools/llvm-mca/llvm-mca.cpp
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D53055.168914.patch
Type: text/x-patch
Size: 9085 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20181010/fcd5c2b0/attachment.bin>
More information about the llvm-commits
mailing list