of expressions on the right, each of which must be single-valued, and the
<i>n</i>th expression on the right is assigned to the <i>n</i>th
operand on the left:
</p>

<pre>
one, two, three = '一', '二', '三'
</pre>

<p>
The <a href="#Blank_identifier">blank identifier</a> provides a way to
ignore right-hand side values in an assignment:
</p>

<pre>

pkg syscall (freebsd-arm64), const RTV_SSTHRESH = 32
pkg syscall (freebsd-arm64), const RTV_SSTHRESH ideal-int
pkg syscall (freebsd-arm64), const RTV_WEIGHT = 256
pkg syscall (freebsd-arm64), const RTV_WEIGHT ideal-int
pkg syscall (freebsd-arm64), const RUSAGE_CHILDREN = -1
pkg syscall (freebsd-arm64), const RUSAGE_CHILDREN ideal-int
pkg syscall (freebsd-arm64), const RUSAGE_SELF = 0

<code>R0&lt;&lt;16</code>
<br>
<code>R0@&gt;16</code>:
For <code>&lt;&lt;</code>, left shift <code>R0</code> by 16 bits.
The other codes are <code>-&gt;</code> (arithmetic right shift),
<code>&gt;&gt;</code> (logical right shift), and
<code>@&gt;</code> (rotate right).
</li>

<li>
<code>R0-&gt;R1</code>
<br>
<code>R0&gt;&gt;R1</code>
<br>
<code>R0&lt;&lt;R1</code>
<br>
<code>R0@&gt;R1</code>:

pkg debug/elf, const R_PPC64_PLTSEQ_NOTOC R_PPC64 #54345
pkg debug/elf, const R_PPC64_PLTSEQ R_PPC64 #54345
pkg debug/elf, const R_PPC64_REL16_HIGH = 240 #54345
pkg debug/elf, const R_PPC64_REL16_HIGHA = 241 #54345
pkg debug/elf, const R_PPC64_REL16_HIGHA R_PPC64 #54345
pkg debug/elf, const R_PPC64_REL16_HIGHER = 242 #54345
pkg debug/elf, const R_PPC64_REL16_HIGHER34 = 140 #54345

of expressions on the right, each of which must be single-valued, and the
<i>n</i>th expression on the right is assigned to the <i>n</i>th
operand on the left:
</p>

<pre>
one, two, three = '一', '二', '三'
</pre>

<p>
The <a href="#Blank_identifier">blank identifier</a> provides a way to
ignore right-hand side values in an assignment:
</p>

<pre>

			return false
		}
	}
	return true
}

// It would be nice if the error messages always began with
// the standard file:line: prefix,
// but that's not where we are today.
// It might be at the beginning but it might be in the middle of the printed instruction.
var fileLineRE = regexp.MustCompile(`(?:^|\()(testdata[/\\][\da-z]+\.s:\d+)(?:$|\)|:)`)

// Same as in test/run.go
var (