semi-abstract instruction set and turn it into instructions to be
input to the linker.
If you want to see what the instructions look like in assembly for a given architecture, say amd64, there
are many examples in the sources of the standard library, in packages such as
<a href="/pkg/runtime/"><code>runtime</code></a> and
<a href="/pkg/math/big/"><code>math/big</code></a>.

        <constraint name="TARGET" within="" contains="" />
      </replaceConfiguration>

          <version>1.0.0+</version>
          <type>String</type>
          <description>
            <![CDATA[
            A repository id or (since Maven 2.0.9) an expression matching one or many repository ids to mirror, e.g.,
            <code>central</code> or <code>*,!repo1</code>.

<pre>
i := *p
if i &lt; 0 || i &gt;= len(funcs) {
	panic("invalid function index")
}
... complex code ...
// compiler must NOT reload i = *p here
funcs[i]()
</pre>

<p>
If the complex code needs many registers, a compiler for single-threaded programs
could discard <code>i</code> without saving a copy and then reload
<code>i = *p</code> just before
<code>funcs[i]()</code>.