a number of productions. Go programs may omit most of these semicolons
using the following two rules:
</p>

<ol>
<li>
When the input is broken into tokens, a semicolon is automatically inserted
into the token stream immediately after a line's final token if that token is
<ul>
	<li>an
	    <a href="#Identifiers">identifier</a>
	</li>

	<li>an
	    <a href="#Integer_literals">integer</a>,

	}

	data1, data2, pax, sparse := ss[0], ss[1], ss[2], ss[3]
	data2 += strings.Repeat("\x00", 10*512)
	trash := strings.Repeat("garbage ", 64) // Exactly 512 bytes

	vectors := []struct {
		input string // Input stream
		cnt   int    // Expected number of headers read
		err   error  // Expected error outcome
	}{
		{"", 0, io.EOF}, // Empty file is a "valid" tar file
		{data1[:511], 0, io.ErrUnexpectedEOF},

pkg crypto/cipher, func NewCBCEncrypter(Block, []uint8) BlockMode
pkg crypto/cipher, func NewCFBDecrypter(Block, []uint8) Stream
pkg crypto/cipher, func NewCFBEncrypter(Block, []uint8) Stream
pkg crypto/cipher, func NewCTR(Block, []uint8) Stream
pkg crypto/cipher, func NewOFB(Block, []uint8) Stream
pkg crypto/cipher, method (StreamReader) Read([]uint8) (int, error)
pkg crypto/cipher, method (StreamWriter) Close() error

	magicUSTAR, versionUSTAR = "ustar\x00", "00"
	trailerSTAR              = "tar\x00"
)

// Size constants from various tar specifications.
const (
	blockSize  = 512 // Size of each block in a tar stream
	nameSize   = 100 // Max length of the name field in USTAR format
	prefixSize = 155 // Max length of the prefix field in USTAR format

	// Max length of a special file (PAX header, GNU long name or link).

but only worthwhile if it's likely the instruction will be used again.
Instead, for simple one-off cases, it's possible to use the <code>BYTE</code>
and <code>WORD</code> directives
to lay down explicit data into the instruction stream within a <code>TEXT</code>.
Here's how the 386 runtime defines the 64-bit atomic load function.
</p>

<pre>
// uint64 atomicload64(uint64 volatile* addr);
// so actually

a number of productions. Go programs may omit most of these semicolons
using the following two rules:
</p>

<ol>
<li>
When the input is broken into tokens, a semicolon is automatically inserted
into the token stream immediately after a line's final token if that token is
<ul>
	<li>an
	    <a href="#Identifiers">identifier</a>
	</li>

	<li>an
	    <a href="#Integer_literals">integer</a>,

pkg syscall, const SIGTERM = 15
pkg syscall, const SIGTRAP = 5
pkg syscall, const SOCK_DGRAM = 2
pkg syscall, const SOCK_RAW = 3
pkg syscall, const SOCK_SEQPACKET = 5
pkg syscall, const SOCK_STREAM = 1
pkg syscall, const S_IFBLK = 24576
pkg syscall, const S_IFCHR = 8192
pkg syscall, const S_IFDIR = 16384
pkg syscall, const S_IFIFO = 4096
pkg syscall, const S_IFLNK = 40960

func discard(r io.Reader, n int64) error {
	// If possible, Seek to the last byte before the end of the data section.
	// Do this because Seek is often lazy about reporting errors; this will mask
	// the fact that the stream may be truncated. We can rely on the
	// io.CopyN done shortly afterwards to trigger any IO errors.
	var seekSkipped int64 // Number of bytes skipped via Seek
	if sr, ok := r.(io.Seeker); ok && n > 1 {

pkg compress/zlib, type Resetter interface { Reset }
pkg compress/zlib, type Resetter interface, Reset(io.Reader, []uint8) error

# CL 159120044 compress/gzip: allow stopping at end of first stream, Russ Cox <******@****.***>
pkg compress/gzip, method (*Reader) Multistream(bool)

# CL 138800043 crypto: Add SHA3 functions in go.crypto/sha3 to the Hash enum., David Leon Gil <******@****.***>
pkg crypto, const SHA3_224 = 10

// the text of the most recently returned token is, and where it was found.
// The underlying scanner elides all spaces except newline, so the input looks like a stream of
// Tokens; original spacing is lost but we don't need it.
type TokenReader interface {
	// Next returns the next token.
	Next() ScanToken
	// The following methods all refer to the most recent token returned by Next.