diff options
| author | Andrew Lenharth <andrewl@lenharth.org> | 2005-03-28 20:05:49 +0000 |
|---|---|---|
| committer | Andrew Lenharth <andrewl@lenharth.org> | 2005-03-28 20:05:49 +0000 |
| commit | 7f4ec3b2e3157e6a0798f3e95a3961bfa6ef66b6 (patch) | |
| tree | fdff3dc2930839353a7c5e2fe45fbccfa060e8a8 /docs/LangRef.html | |
| parent | 9db505ca9dca58421f3b819ced5112789dafba31 (diff) | |
| download | external_llvm-7f4ec3b2e3157e6a0798f3e95a3961bfa6ef66b6.zip external_llvm-7f4ec3b2e3157e6a0798f3e95a3961bfa6ef66b6.tar.gz external_llvm-7f4ec3b2e3157e6a0798f3e95a3961bfa6ef66b6.tar.bz2 | |
First step in adding pcmarker intrinsic. Second step (soon) is adding backend support.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@20900 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs/LangRef.html')
| -rw-r--r-- | docs/LangRef.html | 41 |
1 files changed, 41 insertions, 0 deletions
diff --git a/docs/LangRef.html b/docs/LangRef.html index 807c751..b7bbac3 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -126,6 +126,7 @@ <li><a href="#i_returnaddress">'<tt>llvm.returnaddress</tt>' Intrinsic</a></li> <li><a href="#i_frameaddress">'<tt>llvm.frameaddress</tt>' Intrinsic</a></li> <li><a href="#i_prefetch">'<tt>llvm.prefetch</tt>' Intrinsic</a></li> + <li><a href="#i_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a></li> </ol> </li> <li><a href="#int_os">Operating System Intrinsics</a> @@ -2548,6 +2549,46 @@ performance. </div> +<!-- _______________________________________________________________________ --> +<div class="doc_subsubsection"> + <a name="i_pcmarker">'<tt>llvm.pcmarker</tt>' Intrinsic</a> +</div> + +<div class="doc_text"> + +<h5>Syntax:</h5> +<pre> + call void (uint)* %llvm.pcmarker( uint <id> ) +</pre> + +<h5>Overview:</h5> + + +<p> +The '<tt>llvm.pcmarker</tt>' intrinsic is a method to export a PC in a region of +code to simulators and other tools. The method is target specific, but it is +expected that the marker will use exported symbols to transmit the PC of the marker. +The marker makes no guaranties that it will remain with any specific instruction +after optimizations. It is possible that the presense of a marker will inhibit +optimizations. The intended use is to be inserted after optmizations to allow +corrolations of simulation runs. +</p> + +<h5>Arguments:</h5> + +<p> +<tt>id</tt> is a numerical id identifying the marker. +</p> + +<h5>Semantics:</h5> + +<p> +This intrinsic does not modify the behavior of the program. Backends that do not +support this intrinisic may ignore it. +</p> + +</div> + <!-- ======================================================================= --> <div class="doc_subsection"> |