summaryrefslogtreecommitdiffstats
path: root/llvm/docs/Statepoints.rst
diff options
context:
space:
mode:
Diffstat (limited to 'llvm/docs/Statepoints.rst')
-rw-r--r--llvm/docs/Statepoints.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/llvm/docs/Statepoints.rst b/llvm/docs/Statepoints.rst
index 73e09ae8b62..6ed4e46b73b 100644
--- a/llvm/docs/Statepoints.rst
+++ b/llvm/docs/Statepoints.rst
@@ -172,7 +172,7 @@ SSA value ``%obj.relocated`` which represents the potentially changed value of
``%obj`` after the safepoint and update any following uses appropriately. The
resulting relocation sequence is:
-.. code-block:: text
+.. code-block:: llvm
define i8 addrspace(1)* @test1(i8 addrspace(1)* %obj)
gc "statepoint-example" {
@@ -273,7 +273,7 @@ afterwards.
If we extend our previous example to include a pointless derived pointer,
we get:
-.. code-block:: text
+.. code-block:: llvm
define i8 addrspace(1)* @test1(i8 addrspace(1)* %obj)
gc "statepoint-example" {
@@ -319,7 +319,7 @@ Let's assume a hypothetical GC--somewhat unimaginatively named "hypothetical-gc"
--that requires that a TLS variable must be written to before and after a call
to unmanaged code. The resulting relocation sequence is:
-.. code-block:: text
+.. code-block:: llvm
@flag = thread_local global i32 0, align 4
@@ -702,7 +702,7 @@ whitelist or use one of the predefined ones.
As an example, given this code:
-.. code-block:: text
+.. code-block:: llvm
define i8 addrspace(1)* @test1(i8 addrspace(1)* %obj)
gc "statepoint-example" {
@@ -712,7 +712,7 @@ As an example, given this code:
The pass would produce this IR:
-.. code-block:: text
+.. code-block:: llvm
define i8 addrspace(1)* @test1(i8 addrspace(1)* %obj)
gc "statepoint-example" {
@@ -789,7 +789,7 @@ As an example, given input IR of the following:
This pass would produce the following IR:
-.. code-block:: text
+.. code-block:: llvm
define void @test() gc "statepoint-example" {
call void @do_safepoint()
OpenPOWER on IntegriCloud