summaryrefslogtreecommitdiffstats
path: root/llvm/docs
diff options
context:
space:
mode:
authorDiego Novillo <dnovillo@google.com>2015-05-13 15:13:45 +0000
committerDiego Novillo <dnovillo@google.com>2015-05-13 15:13:45 +0000
commit2567f3d0fb1f2812f99111ecd67d228ccae42c49 (patch)
tree365e1e894c459f612277ef5da02f2f53ecd2d384 /llvm/docs
parentbbcf75e59eaa027251e060043067257c64a866ba (diff)
downloadbcm5719-llvm-2567f3d0fb1f2812f99111ecd67d228ccae42c49.tar.gz
bcm5719-llvm-2567f3d0fb1f2812f99111ecd67d228ccae42c49.zip
Add function entry count metadata.
Summary: This adds three Function methods to handle function entry counts: setEntryCount() and getEntryCount(). Entry counts are stored under the MD_prof metadata node with the name "function_entry_count". They are unsigned 64 bit values set by profilers (instrumentation and sample profiler changes coming up). Added documentation for new profile metadata and tests. Reviewers: dexonsmith, bogner Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D9628 llvm-svn: 237260
Diffstat (limited to 'llvm/docs')
-rw-r--r--llvm/docs/BranchWeightMetadata.rst23
1 files changed, 23 insertions, 0 deletions
diff --git a/llvm/docs/BranchWeightMetadata.rst b/llvm/docs/BranchWeightMetadata.rst
index aff7923d186..2ebc6c32416 100644
--- a/llvm/docs/BranchWeightMetadata.rst
+++ b/llvm/docs/BranchWeightMetadata.rst
@@ -115,3 +115,26 @@ CFG Modifications
Branch Weight Metatada is not proof against CFG changes. If terminator operands'
are changed some action should be taken. In other case some misoptimizations may
occur due to incorrent branch prediction information.
+
+Function Entry Counts
+=====================
+
+To allow comparing different functions durint inter-procedural analysis and
+optimization, ``MD_prof`` nodes can also be assigned to a function definition.
+The first operand is a string indicating the name of the associated counter.
+
+Currently, one counter is supported: "function_entry_count". This is a 64-bit
+counter that indicates the number of times that this function was invoked (in
+the case of instrumentation-based profiles). In the case of sampling-based
+profiles, this counter is an approximation of how many times the function was
+invoked.
+
+For example, in the code below, the instrumentation for function foo()
+indicates that it was called 2,590 times at runtime.
+
+.. code-block:: llvm
+
+ define i32 @foo() !prof !1 {
+ ret i32 0
+ }
+ !1 = !{!"function_entry_count", i64 2590}
OpenPOWER on IntegriCloud