Merge branch 'GP-0_ryanmkurtz_PR-8415_widberg_callother'

This commit is contained in:
Ryan Kurtz
2025-12-03 12:46:26 -05:00
5 changed files with 14 additions and 14 deletions

View File

@@ -60,7 +60,7 @@
</tr>
<tr>
<td></td>
<td><link linkend="cpui_userdefined">USERDEFINED</link></td>
<td><link linkend="cpui_callother">CALLOTHER</link></td>
<td><link linkend="cpui_int_and">INT_AND</link></td>
<td><link linkend="cpui_float_div">FLOAT_DIV</link></td>
</tr>
@@ -3388,9 +3388,9 @@ either the operator is just carried through as a black-box or it serves as a plu
substitution or other specially tailored transformation. Pseudo operators may violate the requirement
placed on other p-code operations that all effects must be explicit.
</para>
<sect2 id="cpui_userdefined"><title>USERDEFINED</title>
<sect2 id="cpui_callother"><title>CALLOTHER</title>
<informalexample>
<table xml:id="userdefined.htmltable" frame="above" width="80%" rules="groups">
<table xml:id="callother.htmltable" frame="above" width="80%" rules="groups">
<col width="23%"/>
<col width="15%"/>
<col width="61%"/>
@@ -3443,14 +3443,14 @@ This is a placeholder for (a family of) user-definable p-code
instructions. It allows p-code instructions to be defined with
semantic actions that are not fully specified. Machine instructions
that are too complicated or too esoteric to fully implement can use
one or more <emphasis role="bold">USERDEFINED</emphasis> instructions
one or more <emphasis role="bold">CALLOTHER</emphasis> instructions
as placeholders for their semantics.
</para>
<para>
The first input parameter input0 is a constant ID assigned by the specification
to a particular semantic action. Depending on how the specification
defines the action associated with the ID,
the <emphasis role="bold">USERDEFINED</emphasis> instruction can take
the <emphasis role="bold">CALLOTHER</emphasis> instruction can take
an arbitrary number of input parameters and optionally have an output
parameter. Exact details are processor and specification dependent.
Ideally, the output parameter is determined by the input

View File

@@ -4299,7 +4299,7 @@ to lowest.
<td>Allocate object of type described by v0.</td>
</tr>
<tr>
<td><code><emphasis>USER_DEFINED</emphasis></code></td>
<td><code><emphasis>CALLOTHER</emphasis></code></td>
<td><code><emphasis>ident</emphasis>(v0,...)</code></td>
<td>User defined operator <emphasis>ident</emphasis>, with functional syntax.</td>
</tr>
@@ -4355,7 +4355,7 @@ The following table lists the basic forms of a semantic statement.
</td>
</tr>
<tr>
<td><code><emphasis>USER_DEFINED</emphasis></code></td>
<td><code><emphasis>CALLOTHER</emphasis></code></td>
<td><code><emphasis>ident</emphasis>(v0,...);</code></td>
<td>Invoke user-defined operation ident as a standalone statement, with no output.</td>
</tr>

View File

@@ -87,7 +87,7 @@
</tr>
<tr>
<td></td>
<td><a class="link" href="pseudo-ops.html#cpui_userdefined" title="USERDEFINED">USERDEFINED</a></td>
<td><a class="link" href="pseudo-ops.html#cpui_callother" title="CALLOTHER">CALLOTHER</a></td>
<td><a class="link" href="pcodedescription.html#cpui_int_and" title="INT_AND">INT_AND</a></td>
<td><a class="link" href="pcodedescription.html#cpui_float_div" title="FLOAT_DIV">FLOAT_DIV</a></td>
</tr>

View File

@@ -38,9 +38,9 @@ placed on other p-code operations that all effects must be explicit.
</p>
<div class="sect2">
<div class="titlepage"><div><div><h3 class="title">
<a name="cpui_userdefined"></a>USERDEFINED</h3></div></div></div>
<a name="cpui_callother"></a>CALLOTHER</h3></div></div></div>
<div class="informalexample"><div class="table">
<a name="userdefined.htmltable"></a><table xml:id="userdefined.htmltable" frame="above" width="80%" rules="groups">
<a name="callother.htmltable"></a><table xml:id="callother.htmltable" frame="above" width="80%" rules="groups">
<col width="23%">
<col width="15%">
<col width="61%">
@@ -91,14 +91,14 @@ This is a placeholder for (a family of) user-definable p-code
instructions. It allows p-code instructions to be defined with
semantic actions that are not fully specified. Machine instructions
that are too complicated or too esoteric to fully implement can use
one or more <span class="bold"><strong>USERDEFINED</strong></span> instructions
one or more <span class="bold"><strong>CALLOTHER</strong></span> instructions
as placeholders for their semantics.
</p>
<p>
The first input parameter input0 is a constant ID assigned by the specification
to a particular semantic action. Depending on how the specification
defines the action associated with the ID,
the <span class="bold"><strong>USERDEFINED</strong></span> instruction can take
the <span class="bold"><strong>CALLOTHER</strong></span> instruction can take
an arbitrary number of input parameters and optionally have an output
parameter. Exact details are processor and specification dependent.
Ideally, the output parameter is determined by the input

View File

@@ -443,7 +443,7 @@ to lowest.
<td>Allocate object of type described by v0.</td>
</tr>
<tr>
<td><code class="code"><span class="emphasis"><em>USER_DEFINED</em></span></code></td>
<td><code class="code"><span class="emphasis"><em>CALLOTHER</em></span></code></td>
<td><code class="code"><span class="emphasis"><em>ident</em></span>(v0,...)</code></td>
<td>User defined operator <span class="emphasis"><em>ident</em></span>, with functional syntax.</td>
</tr>
@@ -502,7 +502,7 @@ The following table lists the basic forms of a semantic statement.
</td>
</tr>
<tr>
<td><code class="code"><span class="emphasis"><em>USER_DEFINED</em></span></code></td>
<td><code class="code"><span class="emphasis"><em>CALLOTHER</em></span></code></td>
<td><code class="code"><span class="emphasis"><em>ident</em></span>(v0,...);</code></td>
<td>Invoke user-defined operation ident as a standalone statement, with no output.</td>
</tr>