Here is the entry point for the compiler code: https://go.googlesource.com/go/+/master/src/cmd/compile/
And here is the entry point for the linker code: https://go.googlesource.com/go/+/master/src/cmd/link/ Note this is all non-trivial. You do need to know how compilers/linkers work before trying to understand this specific code. On Wed, Dec 13, 2017 at 10:55 AM Compiler <erfangnuli...@gmail.com> wrote: > may be show me github link source file then at they is generate binary... > at GOLANG sources. > > On Wednesday, December 13, 2017 at 10:03:27 PM UTC+3:30, Andy Balholm > wrote: >> >> By “Machine Code” I mean that “go build” or “go install” generates an >> executable file that is ready for the target operating system and CPU to >> run directly. On Windows, it generates a .EXE file. On Unix-like operating >> systems it generates a “binary executable” file (which is basically the >> same thing, but it doesn’t have a suffix to identify the file type like >> Windows uses). >> >> (Internally, this process is divided into two steps, called “compile” and >> “link.” The compile step generates the machine code needed by the target >> CPU; the link step arranges this machine code into the file format that the >> target operating system expects.) >> >> Andy >> >> -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
