[PATCH] D107128: Explain the symbols of basic block clusters with an example in the header comments.
Rahman Lavaee via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Fri Jul 30 12:08:31 PDT 2021
This revision was automatically updated to reflect the committed changes.
Closed by commit rG2256b359d793: Explain the symbols of basic block clusters with an example in the header… (authored by rahmanl).
Repository:
rG LLVM Github Monorepo
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D107128/new/
https://reviews.llvm.org/D107128
Files:
llvm/lib/CodeGen/BasicBlockSections.cpp
Index: llvm/lib/CodeGen/BasicBlockSections.cpp
===================================================================
--- llvm/lib/CodeGen/BasicBlockSections.cpp
+++ llvm/lib/CodeGen/BasicBlockSections.cpp
@@ -21,9 +21,21 @@
// clusters of basic blocks. Every cluster will be emitted into a separate
// section with its basic blocks sequenced in the given order. To get the
// optimized performance, the clusters must form an optimal BB layout for the
-// function. Every cluster's section is labeled with a symbol to allow the
-// linker to reorder the sections in any arbitrary sequence. A global order of
-// these sections would encapsulate the function layout.
+// function. We insert a symbol at the beginning of every cluster's section to
+// allow the linker to reorder the sections in any arbitrary sequence. A global
+// order of these sections would encapsulate the function layout.
+// For example, consider the following clusters for a function foo (consisting
+// of 6 basic blocks 0, 1, ..., 5).
+//
+// 0 2
+// 1 3 5
+//
+// * Basic blocks 0 and 2 are placed in one section with symbol `foo`
+// referencing the beginning of this section.
+// * Basic blocks 1, 3, 5 are placed in a separate section. A new symbol
+// `foo.__part.1` will reference the beginning of this section.
+// * Basic block 4 (note that it is not referenced in the list) is placed in
+// one section, and a new symbol `foo.cold` will point to it.
//
// There are a couple of challenges to be addressed:
//
-------------- next part --------------
A non-text attachment was scrubbed...
Name: D107128.363179.patch
Type: text/x-patch
Size: 1503 bytes
Desc: not available
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20210730/bfbde774/attachment.bin>
More information about the llvm-commits
mailing list