Black Lives Matter. Support the Equal Justice Initiative.

Source file src/cmd/compile/doc.go

Documentation: cmd/compile

     1  // Copyright 2009 The Go Authors. All rights reserved.
     2  // Use of this source code is governed by a BSD-style
     3  // license that can be found in the LICENSE file.
     5  /*
     6  Compile, typically invoked as ``go tool compile,'' compiles a single Go package
     7  comprising the files named on the command line. It then writes a single
     8  object file named for the basename of the first source file with a .o suffix.
     9  The object file can then be combined with other objects into a package archive
    10  or passed directly to the linker (``go tool link''). If invoked with -pack, the compiler
    11  writes an archive directly, bypassing the intermediate object file.
    13  The generated files contain type information about the symbols exported by
    14  the package and about types used by symbols imported by the package from
    15  other packages. It is therefore not necessary when compiling client C of
    16  package P to read the files of P's dependencies, only the compiled output of P.
    18  Command Line
    20  Usage:
    22  	go tool compile [flags] file...
    24  The specified files must be Go source files and all part of the same package.
    25  The same compiler is used for all target operating systems and architectures.
    26  The GOOS and GOARCH environment variables set the desired target.
    28  Flags:
    30  	-D path
    31  		Set relative path for local imports.
    32  	-I dir1 -I dir2
    33  		Search for imported packages in dir1, dir2, etc,
    34  		after consulting $GOROOT/pkg/$GOOS_$GOARCH.
    35  	-L
    36  		Show complete file path in error messages.
    37  	-N
    38  		Disable optimizations.
    39  	-S
    40  		Print assembly listing to standard output (code only).
    41  	-S -S
    42  		Print assembly listing to standard output (code and data).
    43  	-V
    44  		Print compiler version and exit.
    45  	-asmhdr file
    46  		Write assembly header to file.
    47  	-buildid id
    48  		Record id as the build id in the export metadata.
    49  	-blockprofile file
    50  		Write block profile for the compilation to file.
    51  	-c int
    52  		Concurrency during compilation. Set 1 for no concurrency (default is 1).
    53  	-complete
    54  		Assume package has no non-Go components.
    55  	-cpuprofile file
    56  		Write a CPU profile for the compilation to file.
    57  	-dynlink
    58  		Allow references to Go symbols in shared libraries (experimental).
    59  	-e
    60  		Remove the limit on the number of errors reported (default limit is 10).
    61  	-goversion string
    62  		Specify required go tool version of the runtime.
    63  		Exits when the runtime go version does not match goversion.
    64  	-h
    65  		Halt with a stack trace at the first error detected.
    66  	-importcfg file
    67  		Read import configuration from file.
    68  		In the file, set importmap, packagefile to specify import resolution.
    69  	-importmap old=new
    70  		Interpret import "old" as import "new" during compilation.
    71  		The option may be repeated to add multiple mappings.
    72  	-installsuffix suffix
    73  		Look for packages in $GOROOT/pkg/$GOOS_$GOARCH_suffix
    74  		instead of $GOROOT/pkg/$GOOS_$GOARCH.
    75  	-l
    76  		Disable inlining.
    77  	-lang version
    78  		Set language version to compile, as in -lang=go1.12.
    79  		Default is current version.
    80  	-linkobj file
    81  		Write linker-specific object to file and compiler-specific
    82  		object to usual output file (as specified by -o).
    83  		Without this flag, the -o output is a combination of both
    84  		linker and compiler input.
    85  	-m
    86  		Print optimization decisions.
    87  	-memprofile file
    88  		Write memory profile for the compilation to file.
    89  	-memprofilerate rate
    90  		Set runtime.MemProfileRate for the compilation to rate.
    91  	-msan
    92  		Insert calls to C/C++ memory sanitizer.
    93  	-mutexprofile file
    94  		Write mutex profile for the compilation to file.
    95  	-nolocalimports
    96  		Disallow local (relative) imports.
    97  	-o file
    98  		Write object to file (default file.o or, with -pack, file.a).
    99  	-p path
   100  		Set expected package import path for the code being compiled,
   101  		and diagnose imports that would cause a circular dependency.
   102  	-pack
   103  		Write a package (archive) file rather than an object file
   104  	-race
   105  		Compile with race detector enabled.
   106  	-s
   107  		Warn about composite literals that can be simplified.
   108  	-shared
   109  		Generate code that can be linked into a shared library.
   110  	-spectre list
   111  		Enable spectre mitigations in list (all, index, ret).
   112  	-traceprofile file
   113  		Write an execution trace to file.
   114  	-trimpath prefix
   115  		Remove prefix from recorded source file paths.
   117  Flags related to debugging information:
   119  	-dwarf
   120  		Generate DWARF symbols.
   121  	-dwarflocationlists
   122  		Add location lists to DWARF in optimized mode.
   123  	-gendwarfinl int
   124  		Generate DWARF inline info records (default 2).
   126  Flags to debug the compiler itself:
   128  	-E
   129  		Debug symbol export.
   130  	-K
   131  		Debug missing line numbers.
   132  	-d list
   133  		Print debug information about items in list. Try -d help for further information.
   134  	-live
   135  		Debug liveness analysis.
   136  	-v
   137  		Increase debug verbosity.
   138  	-%
   139  		Debug non-static initializers.
   140  	-W
   141  		Debug parse tree after type checking.
   142  	-f
   143  		Debug stack frames.
   144  	-i
   145  		Debug line number stack.
   146  	-j
   147  		Debug runtime-initialized variables.
   148  	-r
   149  		Debug generated wrappers.
   150  	-w
   151  		Debug type checking.
   153  Compiler Directives
   155  The compiler accepts directives in the form of comments.
   156  To distinguish them from non-directive comments, directives
   157  require no space between the comment opening and the name of the directive. However, since
   158  they are comments, tools unaware of the directive convention or of a particular
   159  directive can skip over a directive like any other comment.
   160  */
   161  // Line directives come in several forms:
   162  //
   163  // 	//line :line
   164  // 	//line :line:col
   165  // 	//line filename:line
   166  // 	//line filename:line:col
   167  // 	/*line :line*/
   168  // 	/*line :line:col*/
   169  // 	/*line filename:line*/
   170  // 	/*line filename:line:col*/
   171  //
   172  // In order to be recognized as a line directive, the comment must start with
   173  // //line or /*line followed by a space, and must contain at least one colon.
   174  // The //line form must start at the beginning of a line.
   175  // A line directive specifies the source position for the character immediately following
   176  // the comment as having come from the specified file, line and column:
   177  // For a //line comment, this is the first character of the next line, and
   178  // for a /*line comment this is the character position immediately following the closing */.
   179  // If no filename is given, the recorded filename is empty if there is also no column number;
   180  // otherwise it is the most recently recorded filename (actual filename or filename specified
   181  // by previous line directive).
   182  // If a line directive doesn't specify a column number, the column is "unknown" until
   183  // the next directive and the compiler does not report column numbers for that range.
   184  // The line directive text is interpreted from the back: First the trailing :ddd is peeled
   185  // off from the directive text if ddd is a valid number > 0. Then the second :ddd
   186  // is peeled off the same way if it is valid. Anything before that is considered the filename
   187  // (possibly including blanks and colons). Invalid line or column values are reported as errors.
   188  //
   189  // Examples:
   190  //
   191  //	//line foo.go:10      the filename is foo.go, and the line number is 10 for the next line
   192  //	//line C:foo.go:10    colons are permitted in filenames, here the filename is C:foo.go, and the line is 10
   193  //	//line  a:100 :10     blanks are permitted in filenames, here the filename is " a:100 " (excluding quotes)
   194  //	/*line :10:20*/x      the position of x is in the current file with line number 10 and column number 20
   195  //	/*line foo: 10 */     this comment is recognized as invalid line directive (extra blanks around line number)
   196  //
   197  // Line directives typically appear in machine-generated code, so that compilers and debuggers
   198  // will report positions in the original input to the generator.
   199  /*
   200  The line directive is a historical special case; all other directives are of the form
   201  //go:name, indicating that they are defined by the Go toolchain.
   202  Each directive must be placed its own line, with only leading spaces and tabs
   203  allowed before the comment.
   204  Each directive applies to the Go code that immediately follows it,
   205  which typically must be a declaration.
   207  	//go:noescape
   209  The //go:noescape directive must be followed by a function declaration without
   210  a body (meaning that the function has an implementation not written in Go).
   211  It specifies that the function does not allow any of the pointers passed as
   212  arguments to escape into the heap or into the values returned from the function.
   213  This information can be used during the compiler's escape analysis of Go code
   214  calling the function.
   216  	//go:uintptrescapes
   218  The //go:uintptrescapes directive must be followed by a function declaration.
   219  It specifies that the function's uintptr arguments may be pointer values
   220  that have been converted to uintptr and must be treated as such by the
   221  garbage collector. The conversion from pointer to uintptr must appear in
   222  the argument list of any call to this function. This directive is necessary
   223  for some low-level system call implementations and should be avoided otherwise.
   225  	//go:noinline
   227  The //go:noinline directive must be followed by a function declaration.
   228  It specifies that calls to the function should not be inlined, overriding
   229  the compiler's usual optimization rules. This is typically only needed
   230  for special runtime functions or when debugging the compiler.
   232  	//go:norace
   234  The //go:norace directive must be followed by a function declaration.
   235  It specifies that the function's memory accesses must be ignored by the
   236  race detector. This is most commonly used in low-level code invoked
   237  at times when it is unsafe to call into the race detector runtime.
   239  	//go:nosplit
   241  The //go:nosplit directive must be followed by a function declaration.
   242  It specifies that the function must omit its usual stack overflow check.
   243  This is most commonly used by low-level runtime code invoked
   244  at times when it is unsafe for the calling goroutine to be preempted.
   246  	//go:linkname localname []
   248  This special directive does not apply to the Go code that follows it.
   249  Instead, the //go:linkname directive instructs the compiler to use ``''
   250  as the object file symbol name for the variable or function declared as ``localname''
   251  in the source code.
   252  If the ``'' argument is omitted, the directive uses the
   253  symbol's default object file symbol name and only has the effect of making
   254  the symbol accessible to other packages.
   255  Because this directive can subvert the type system and package
   256  modularity, it is only enabled in files that have imported "unsafe".
   257  */
   258  package main

View as plain text