1 files changed, 100 insertions, 0 deletions
diff --git a/docs/opcodes/opcode-0f-return.html b/docs/opcodes/opcode-0f-return.html
new file mode 100644
index 000000000..33e0b7c2e
--- /dev/null
+++ b/docs/opcodes/opcode-0f-return.html
@@ -0,0 +1,100 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
+
+<html>
+
+<head>
+<title>return</title>
+<link rel=stylesheet href="opcode.css">
+</head>
+
+<body>
+
+<h1>return</h1>
+
+<h2>Purpose</h2>
+
+<p>
+Return from a single-width (32-bit) non-object value-returning method.
+</p>
+
+<h2>Details</h2>
+
+<table class="instruc">
+<thead>
+<tr>
+  <th>Op &amp; Format</th>
+  <th>Mnemonic / Syntax</th>
+  <th>Arguments</th>
+</tr>
+</thead>
+<tbody>
+<tr>
+  <td>0f 11x</td>
+  <td>return vAA</td>
+  <td><code>A:</code> return value register (8 bits)</td>
+</tr>
+</tbody>
+</table>
+
+<h2>Constraints</h2>
+
+<ul>
+  <li>
+    The return type of the current method must not be double, long, or a
+    reference.
+  </li>
+  <li>
+    A must be a valid register index in the current stack frame.
+  </li>
+  <li>
+    Register vA must not be part of a register pair.
+  </li>
+  <li>
+    The type of vA must match the return type of the method.
+  </li>
+</ul> 
+    
+<h2>Behavior</h2>
+
+<ul>
+  <li>
+    If the method is synchronized, the object's monitor is released in a way
+    similar to the monitor-exit instruction.
+  </li>
+  <li>
+    The stack frame of the current method invocation is removed from the stack.
+    This includes all its registers becoming invalid.
+  </li>
+  <li>
+    If the stack is now empty, the current thread terminates.
+  </li>
+  <li>
+    Otherwise, the following happens:
+    <ul>
+      <li>
+        The stack frame that caused this method invocation becomes valid. This
+        includes all its registers and their old values.
+      </li>
+      <li>
+        Execution continues at the bytecode instruction immediately following
+        the invoke-kind or invoke-kind/range instruction that caused this
+        method invocation.
+      </li>
+      <li>
+        The return value can be consumed by (exactly) the first instruction
+        following the invoke-kind or invoke-kind/range instruction that caused
+        this method invocation, and this instructions needs to be a move-result
+        instruction.
+      </li>
+    </ul>
+  </li>
+</ul>
+ 
+<h2>Exceptions</h2>
+
+<p>
+None.
+</p>
+
+</body>
+</html>