Lines Matching refs:gcc
407 -debug-gcc
489 Cgo first invokes gcc -E -dM on the preamble, in order to find out
595 x.cgo2.c # for gcc
596 y.cgo2.c # for gcc
597 _cgo_defun.c # for gcc (if -gccgo)
598 _cgo_export.c # for gcc
599 _cgo_export.h # for gcc
600 _cgo_main.c # for gcc
616 to make a switch from the Go runtime world to the system C (GCC-based)
634 file compiled by gcc, the file x.cgo2.c:
653 Once the _cgo_export.c and *.cgo2.c files have been compiled with gcc,
674 code generated for gcc. The build process links this stub, along with
692 _all.o # gcc-compiled object for _cgo_export.c, *.cgo2.c
707 that gcc is not needed after the package is compiled. For example,
709 by libc. Although gcc is needed to compile package net, gcc is not
727 to a gcc-compiled function that can be called early during program
728 startup, and _cgo_thread_start to a gcc-compiled function that can be
746 file containing it. Then it invokes the host linker (usually gcc) to
753 binary. When cgo is involved, the compile step already requires gcc, so
754 it is not problematic for the link step to require gcc too.
759 imports net without requiring gcc to be present at link time. (In this
764 This conflict between functionality and the gcc requirement means we
849 In external linking mode, invoke the host linker (usually gcc)
851 Note that the arguments are for "gcc", not "ld".
882 // compiled by gcc, into foo.cgo2.o
942 needing gcc available. The second rule means that a build of a
952 into fields, or else "gcc". The specific host linker command line can
