Re: [go-nuts] About Go Compiler!
Performance of C with Optimize not better of Go at more time?! so why re-write golang in go? On Monday, February 19, 2018 at 3:54:08 AM UTC+3:30, Compiler wrote: > > When Golang using *bootstrapping **technique* , performance not Decrease? > > On Monday, February 19, 2018 at 3:42:18 AM UTC+3:30, Compiler wrote: >> >> *bootstrapping* is the technique for producing a self-compiling compiler >> <https://en.wikipedia.org/wiki/Self-hosting_compiler> >> >> On Monday, February 19, 2018 at 3:40:54 AM UTC+3:30, Compiler wrote: >>> >>> whats difference between self-hosting compiler vs Bootstrapping compiler? >>> >>> https://en.wikipedia.org/wiki/Bootstrapping_(compilers) >>> >>> On Monday, February 19, 2018 at 3:34:48 AM UTC+3:30, Michael Jones wrote: >>>> >>>> much better! i suggest Google searches about bootstrapping, >>>> self-hosting, and security. >>>> >>> -- 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.
Re: [go-nuts] About Go Compiler!
When Golang using *bootstrapping **technique* , performance not Decrease? On Monday, February 19, 2018 at 3:42:18 AM UTC+3:30, Compiler wrote: > > *bootstrapping* is the technique for producing a self-compiling compiler > <https://en.wikipedia.org/wiki/Self-hosting_compiler> > > On Monday, February 19, 2018 at 3:40:54 AM UTC+3:30, Compiler wrote: >> >> whats difference between self-hosting compiler vs Bootstrapping compiler? >> >> https://en.wikipedia.org/wiki/Bootstrapping_(compilers) >> >> On Monday, February 19, 2018 at 3:34:48 AM UTC+3:30, Michael Jones wrote: >>> >>> much better! i suggest Google searches about bootstrapping, >>> self-hosting, and security. >>> >> -- 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.
Re: [go-nuts] About Go Compiler!
*bootstrapping* is the technique for producing a self-compiling compiler <https://en.wikipedia.org/wiki/Self-hosting_compiler> On Monday, February 19, 2018 at 3:40:54 AM UTC+3:30, Compiler wrote: > > whats difference between self-hosting compiler vs Bootstrapping compiler? > > https://en.wikipedia.org/wiki/Bootstrapping_(compilers) > > On Monday, February 19, 2018 at 3:34:48 AM UTC+3:30, Michael Jones wrote: >> >> much better! i suggest Google searches about bootstrapping, >> self-hosting, and security. >> > -- 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.
Re: [go-nuts] About Go Compiler!
whats difference between self-hosting compiler vs Bootstrapping compiler? https://en.wikipedia.org/wiki/Bootstrapping_(compilers) On Monday, February 19, 2018 at 3:34:48 AM UTC+3:30, Michael Jones wrote: > > much better! i suggest Google searches about bootstrapping, self-hosting, > and security. > -- 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.
Re: [go-nuts] About Go Compiler!
I have some experience in writing lexer,parser,interpreter,optimize. I've also worked generate output code(example one language to another). currently example i'm design a interpreter and for final step( generate output file) using another compiler. i'm want know more about compiler... and trying them. I mean the compiler : self compiler On Monday, February 19, 2018 at 3:22:27 AM UTC+3:30, Dave Cheney wrote: > > Stop. > > What do you want to do? > > Do you want to write a C compiler ? > > On Monday, 19 February 2018 10:47:24 UTC+11, Compiler wrote: >> >> https://groups.google.com/forum/#!topic/golang-nuts/24pSm-B3FqU >> >> On Monday, February 19, 2018 at 3:14:48 AM UTC+3:30, Dave Cheney wrote: >>> >>> >>> Who is they? Can you give some more context. >>> >> -- 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.
Re: [go-nuts] About Go Compiler!
Woow, for Generate output file(executable file) Using only Asm? So GoLang Using : 1. *Go: *Runtime Libs 2. *ASM: Only *Generate output file(executable file) 3. *OwnC: * On Monday, February 19, 2018 at 3:14:48 AM UTC+3:30, Dave Cheney wrote: > > By tradition assembly files have .s and .S extensions > -- 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.
Re: [go-nuts] About Go Compiler!
How can trying this? Do not have an idea about it? On Monday, February 19, 2018 at 3:10:04 AM UTC+3:30, Dave Cheney wrote: > > In theory, yes. In practice, I doubt it. > > On Monday, 19 February 2018 10:37:14 UTC+11, Compiler wrote: >> >> Can build only c(own) compiler using a c compiler(like gcc) without go >> from this source?! >> >> >> On Monday, February 19, 2018 at 2:48:26 AM UTC+3:30, Dave Cheney wrote: >>> >>> I feel like we’ve had this same discussion a few months ago. >>> >>> Ian has mentioned that go 1.4 is no longer in use (it exists only in a >>> very special case or bootstrapping from source). >>> >>> Can you please give some context to your questions so we may assist you >>> better. >> >> -- 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.
Re: [go-nuts] About Go Compiler!
Assembly?! but not exist many `.asm` files at source. Also, I had already asked ... And they said they were not with the assembly and is generate executable file using object file. On Monday, February 19, 2018 at 3:08:51 AM UTC+3:30, Dave Cheney wrote: > > > > On Monday, 19 February 2018 10:33:16 UTC+11, Compiler wrote: >> >> /go/src/cmd/cc/ >> this directory is base of c-compiler. >> > > yes, that is where the shared parts of the c compiler lives, the > architecture specific parts were in 5c, 6c, 8c, etc. > > >> >> so not `.c` file in /src/. >> > > You can answer this question yourself by looking in the tarball. The Go > 1.4 runtime was written in a mixture of Go, C, and Assembly. > >> >> On Monday, February 19, 2018 at 3:01:35 AM UTC+3:30, Compiler wrote: >>> >>> mean all `.c` file in /src/ compile using own c-compiler?! >>> >>> On Monday, February 19, 2018 at 2:49:40 AM UTC+3:30, Dave Cheney wrote: >>>> >>>> > which files require go-c compiler? >>>> >>>> The ones in the go 1.4distributuon that end in .c. >>>> >>> -- 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.
Re: [go-nuts] About Go Compiler!
Can build only c(own) compiler using a c compiler(like gcc) without go from this source?! On Monday, February 19, 2018 at 2:48:26 AM UTC+3:30, Dave Cheney wrote: > > I feel like we’ve had this same discussion a few months ago. > > Ian has mentioned that go 1.4 is no longer in use (it exists only in a > very special case or bootstrapping from source). > > Can you please give some context to your questions so we may assist you > better. -- 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.
Re: [go-nuts] About Go Compiler!
/go/src/cmd/cc/ this directory is base of c-compiler. so not `.c` file in /src/. On Monday, February 19, 2018 at 3:01:35 AM UTC+3:30, Compiler wrote: > > mean all `.c` file in /src/ compile using own c-compiler?! > > On Monday, February 19, 2018 at 2:49:40 AM UTC+3:30, Dave Cheney wrote: >> >> > which files require go-c compiler? >> >> The ones in the go 1.4distributuon that end in .c. >> > -- 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.
Re: [go-nuts] About Go Compiler!
mean all `.c` file in /src/ compile using own c-compiler?! On Monday, February 19, 2018 at 2:49:40 AM UTC+3:30, Dave Cheney wrote: > > > which files require go-c compiler? > > The ones in the go 1.4distributuon that end in .c. > -- 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.
Re: [go-nuts] About Go Compiler!
Example : - /go/src/fmt/print.go - /go/src/io/multi.go this files require go compiler (go.y). - which files require go-c compiler(c.y) ?? On Monday, February 19, 2018 at 2:40:36 AM UTC+3:30, Compiler wrote: > > Show me some files at > https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz > then require go-c compiler. > > On Monday, February 19, 2018 at 2:35:18 AM UTC+3:30, Compiler wrote: >> >> :like: >> tanks you. >> >> so go.y is for go compiler and cc.y is for go-c compiler. >> >> all `.go` files require go compiler. >> and what files require go-c compiler? >> >> may tell some example file then is go-c? >> >> On Monday, February 19, 2018 at 2:32:02 AM UTC+3:30, Dave Cheney wrote: >>> >>> In Go 1.4 the project contained both .go files and .c files. It shipped >>> with two compilers, a go compiler, called gc, and a c compiler called cc. >>> >>> > /go/src/cmd/gc/go.y >>> >>> This is the input file for the yacc grammar for the Go 1.4 go compiler >>> >>> > /go/src/cmd/cc/cc.y >>> >>> This is the input file for the yacc grammar for the Go 1.4 c compiler >>> >>> The same advice applies to the other two files you mentioned. >>> >>> On Monday, 19 February 2018 09:57:21 UTC+11, Compiler wrote: >>>> >>>> yeah , in go1.4 version,i want know difference between files. >>>> ?! >>>> >>>> On Monday, February 19, 2018 at 2:04:09 AM UTC+3:30, Ian Lance Taylor >>>> wrote: >>>>> >>>>> On Sun, Feb 18, 2018 at 9:23 AM, Compiler <erfang...@gmail.com> >>>>> wrote: >>>>> > #Question >>>>> > >>>>> > What is the difference between using the following two files? >>>>> > >>>>> > /go/src/cmd/gc/go.y >>>>> > /go/src/cmd/cc/cc.y >>>>> > >>>>> > ----- >>>>> > #Question >>>>> > >>>>> > What is the difference between using the following two files? >>>>> > >>>>> > /go/src/cmd/gc/lex.c >>>>> > /go/src/cmd/cc/lex.c >>>>> >>>>> You must be looking at a very old version of Go, as current versions >>>>> of Go do not contain either file. >>>>> >>>>> Old versions of Go shipped with a C compiler that was used to build >>>>> parts of the runtime that were written in C. Those parts were >>>>> rewritten into Go, and Go no longer ships a C compiler. Back then, >>>>> the Go compiler was in cmd/gc and the C compiler was in cmd/cc. >>>>> >>>>> Ian >>>>> >>>> -- 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.
Re: [go-nuts] About Go Compiler!
Show me some files at https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz then require go-c compiler. On Monday, February 19, 2018 at 2:35:18 AM UTC+3:30, Compiler wrote: > > :like: > tanks you. > > so go.y is for go compiler and cc.y is for go-c compiler. > > all `.go` files require go compiler. > and what files require go-c compiler? > > may tell some example file then is go-c? > > On Monday, February 19, 2018 at 2:32:02 AM UTC+3:30, Dave Cheney wrote: >> >> In Go 1.4 the project contained both .go files and .c files. It shipped >> with two compilers, a go compiler, called gc, and a c compiler called cc. >> >> > /go/src/cmd/gc/go.y >> >> This is the input file for the yacc grammar for the Go 1.4 go compiler >> >> > /go/src/cmd/cc/cc.y >> >> This is the input file for the yacc grammar for the Go 1.4 c compiler >> >> The same advice applies to the other two files you mentioned. >> >> On Monday, 19 February 2018 09:57:21 UTC+11, Compiler wrote: >>> >>> yeah , in go1.4 version,i want know difference between files. >>> ?! >>> >>> On Monday, February 19, 2018 at 2:04:09 AM UTC+3:30, Ian Lance Taylor >>> wrote: >>>> >>>> On Sun, Feb 18, 2018 at 9:23 AM, Compiler <erfang...@gmail.com> wrote: >>>> > #Question >>>> > >>>> > What is the difference between using the following two files? >>>> > >>>> > /go/src/cmd/gc/go.y >>>> > /go/src/cmd/cc/cc.y >>>> > >>>> > ----- >>>> > #Question >>>> > >>>> > What is the difference between using the following two files? >>>> > >>>> > /go/src/cmd/gc/lex.c >>>> > /go/src/cmd/cc/lex.c >>>> >>>> You must be looking at a very old version of Go, as current versions >>>> of Go do not contain either file. >>>> >>>> Old versions of Go shipped with a C compiler that was used to build >>>> parts of the runtime that were written in C. Those parts were >>>> rewritten into Go, and Go no longer ships a C compiler. Back then, >>>> the Go compiler was in cmd/gc and the C compiler was in cmd/cc. >>>> >>>> Ian >>>> >>> -- 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.
Re: [go-nuts] About Go Compiler!
:like: tanks you. so go.y is for go compiler and cc.y is for go-c compiler. all `.go` files require go compiler. and what files require go-c compiler? may tell some example file then is go-c? On Monday, February 19, 2018 at 2:32:02 AM UTC+3:30, Dave Cheney wrote: > > In Go 1.4 the project contained both .go files and .c files. It shipped > with two compilers, a go compiler, called gc, and a c compiler called cc. > > > /go/src/cmd/gc/go.y > > This is the input file for the yacc grammar for the Go 1.4 go compiler > > > /go/src/cmd/cc/cc.y > > This is the input file for the yacc grammar for the Go 1.4 c compiler > > The same advice applies to the other two files you mentioned. > > On Monday, 19 February 2018 09:57:21 UTC+11, Compiler wrote: >> >> yeah , in go1.4 version,i want know difference between files. >> ?! >> >> On Monday, February 19, 2018 at 2:04:09 AM UTC+3:30, Ian Lance Taylor >> wrote: >>> >>> On Sun, Feb 18, 2018 at 9:23 AM, Compiler <erfang...@gmail.com> wrote: >>> > #Question >>> > >>> > What is the difference between using the following two files? >>> > >>> > /go/src/cmd/gc/go.y >>> > /go/src/cmd/cc/cc.y >>> > >>> > - >>> > #Question >>> > >>> > What is the difference between using the following two files? >>> > >>> > /go/src/cmd/gc/lex.c >>> > /go/src/cmd/cc/lex.c >>> >>> You must be looking at a very old version of Go, as current versions >>> of Go do not contain either file. >>> >>> Old versions of Go shipped with a C compiler that was used to build >>> parts of the runtime that were written in C. Those parts were >>> rewritten into Go, and Go no longer ships a C compiler. Back then, >>> the Go compiler was in cmd/gc and the C compiler was in cmd/cc. >>> >>> Ian >>> >> -- 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.
Re: [go-nuts] About Go Compiler!
yeah , in go1.4 version,i want know difference between files. ?! On Monday, February 19, 2018 at 2:04:09 AM UTC+3:30, Ian Lance Taylor wrote: > > On Sun, Feb 18, 2018 at 9:23 AM, Compiler <erfang...@gmail.com > > wrote: > > #Question > > > > What is the difference between using the following two files? > > > > /go/src/cmd/gc/go.y > > /go/src/cmd/cc/cc.y > > > > - > > #Question > > > > What is the difference between using the following two files? > > > > /go/src/cmd/gc/lex.c > > /go/src/cmd/cc/lex.c > > You must be looking at a very old version of Go, as current versions > of Go do not contain either file. > > Old versions of Go shipped with a C compiler that was used to build > parts of the runtime that were written in C. Those parts were > rewritten into Go, and Go no longer ships a C compiler. Back then, > the Go compiler was in cmd/gc and the C compiler was in cmd/cc. > > Ian > -- 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.
[go-nuts] Re: Go 1.10 is released
https://golang.org/pkg/plugin/ Not Forget this : Currently plugins are only supported on Linux and macOS. On Friday, February 16, 2018 at 11:06:22 PM UTC+3:30, Andrew Bonventre wrote: > > Hello gophers, > > We just released Go 1.10. > > You can read the announcement blog post here: > https://blog.golang.org/go1.10 > > You can download binary and source distributions from our download page: > https://golang.org/dl/ > > To compile from source using a Git checkout, update to the release with > "git checkout go1.10" and build as usual. > > To find out what has changed, read the release notes: > https://golang.org/doc/go1.10 > > Thanks to everyone who contributed to the release. > > Andy on behalf of the Go Team > -- 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.
[go-nuts] About Go Compiler!
#Question What is the difference between using the following two files? /go/src/cmd/gc/go.y /go/src/cmd/cc/cc.y - #Question What is the difference between using the following two files? /go/src/cmd/gc/lex.c /go/src/cmd/cc/lex.c -- 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.
[go-nuts] Re: Go Generate Vs Go Build!
- https://en.wikipedia.org/wiki/Go_(programming_language)
- go build, which builds Go binaries using only information in the source
files themselves, no separate makefiles
- go test, for unit testing and microbenchmarks
- go fmt, for formatting code
- go get, for retrieving and installing remote packages
- go vet, a static analyzer looking for potential errors in code
- go run, a shortcut for building and executing code
- godoc, for displaying documentation or serving it via HTTP
- gorename, for renaming variables, functions, and so on in a type-safe way
- go generate, a standard way to invoke code generators
Please explain me.
On Monday, December 18, 2017 at 1:03:55 AM UTC+3:30, Compiler wrote:
>
> Hello,
>
> Go Generate Vs Go Build!?!
>
> guest@Base:~/Gits/go-hello$ ls
> hello hello.go
> guest@Base:~/Gits/go-hello$ cat hello.go
> package main
>
> import "fmt"
>
> func main() {
> fmt.Println("Hello, World")
> }
>
> guest@Base:~/Gits/go-hello$ go build hello.go
> guest@Base:~/Gits/go-hello$ go generate hello.go
> guest@Base:~/Gits/go-hello$ ./hello
> Hello, World
>
>
--
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.
[go-nuts] Go Generate Vs Go Build!
Hello,
Go Generate Vs Go Build!?!
guest@Base:~/Gits/go-hello$ ls
hello hello.go
guest@Base:~/Gits/go-hello$ cat hello.go
package main
import "fmt"
func main() {
fmt.Println("Hello, World")
}
guest@Base:~/Gits/go-hello$ go build hello.go
guest@Base:~/Gits/go-hello$ go generate hello.go
guest@Base:~/Gits/go-hello$ ./hello
Hello, World
--
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.
Re: [go-nuts] Go Compiler How Work?!
Tanks you. ==> The technique of generating an object file directly from the compiler Without Generate ASM Code does not have a name. + May be show me a sample/source/tutorial of generate object file Using C?! On Saturday, December 16, 2017 at 5:03:45 AM UTC+3:30, Ian Lance Taylor wrote: > > The technique of generating an object file directly from the compiler > does not have a name. > > Many other compilers do the same thing For example, clang/LLVM does it. > > These questions about how compilers work do not have anything to do > with Go, and I encourage you to take them to some other group. > > Also, no offense, but I encourage you to find somebody who is fluent > in both your language and English to help you write these questions. > It is often very difficult to understand what you are asking. > > Ian > > > On Fri, Dec 15, 2017 at 4:51 PM, Compiler <erfang...@gmail.com > > wrote: > > No Answer?! > > > > > > On Saturday, December 16, 2017 at 3:38:04 AM UTC+3:30, Compiler wrote: > >> > >> hmmm , > >> what is name of this way for generate executable file at compiler? > >> > >> On Saturday, December 16, 2017 at 3:34:27 AM UTC+3:30, andrey > mirtchovski > >> wrote: > >>> > >>> > so go compiler generate what?! > >>> > >>> https://golang.org/cmd/compile/ > >>> > >>> Compile, typically invoked as “go tool compile,” compiles a single Go > >>> package comprising the files named on the command line. It then writes > >>> a single object file named for the basename of the first source file > >>> with a .o suffix. The object file can then be combined with other > >>> objects into a package archive or passed directly to the linker (“go > >>> tool link”). If invoked with -pack, the compiler writes an archive > >>> directly, bypassing the intermediate object file. > > > > -- > > 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...@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.
Re: [go-nuts] Go Compiler How Work?!
No Answer?! On Saturday, December 16, 2017 at 3:38:04 AM UTC+3:30, Compiler wrote: > > hmmm , > what is name of this way for generate executable file at compiler? > > On Saturday, December 16, 2017 at 3:34:27 AM UTC+3:30, andrey mirtchovski > wrote: >> >> > so go compiler generate what?! >> >> https://golang.org/cmd/compile/ >> >> Compile, typically invoked as “go tool compile,” compiles a single Go >> package comprising the files named on the command line. It then writes >> a single object file named for the basename of the first source file >> with a .o suffix. The object file can then be combined with other >> objects into a package archive or passed directly to the linker (“go >> tool link”). If invoked with -pack, the compiler writes an archive >> directly, bypassing the intermediate object file. >> > -- 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.
Re: [go-nuts] Go Compiler How Work?!
Tanks You. https://github.com/kostya/benchmarks Rust in many tests/samples is better of Go.(Performance) On Saturday, December 16, 2017 at 4:07:49 AM UTC+3:30, Bakul Shah wrote: > > Everything you have asked about has been covered multiple > times but you will have to do some research on your own. > May I suggest reading some documentation on the golang.org > website as well as watching go language related videos? You > can also search for related discussions on this mailing list. > > > On Dec 15, 2017, at 4:22 PM, Compiler <erfang...@gmail.com > > wrote: > > > > mean many go developer will switch to Rust? > > > > but RUST is also google's Lang. > > why when google have a good lang why begin write new lang(go)?! > > > > On Saturday, December 16, 2017 at 3:43:58 AM UTC+3:30, Dave Cheney > wrote: > > I think we should all switch to rust. > > > > -- > > 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...@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.
Re: [go-nuts] Go Compiler How Work?!
mean many go developer will switch to Rust? but RUST is also google's Lang. why when google have a good lang why begin write new lang(go)?! On Saturday, December 16, 2017 at 3:43:58 AM UTC+3:30, Dave Cheney wrote: > > I think we should all switch to rust. -- 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.
Re: [go-nuts] Go Compiler How Work?!
hmmm , what is name of this way for generate executable file at compiler? On Saturday, December 16, 2017 at 3:34:27 AM UTC+3:30, andrey mirtchovski wrote: > > > so go compiler generate what?! > > https://golang.org/cmd/compile/ > > Compile, typically invoked as “go tool compile,” compiles a single Go > package comprising the files named on the command line. It then writes > a single object file named for the basename of the first source file > with a .o suffix. The object file can then be combined with other > objects into a package archive or passed directly to the linker (“go > tool link”). If invoked with -pack, the compiler writes an archive > directly, bypassing the intermediate object file. > -- 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.
Re: [go-nuts] Go Compiler How Work?!
what you think about this?! On Saturday, December 16, 2017 at 3:27:24 AM UTC+3:30, Compiler wrote: > > https://github.com/kostya/benchmarks > > at many sample/tests Rust is better of Go.(Performance) > > On Saturday, December 16, 2017 at 3:22:14 AM UTC+3:30, andrey mirtchovski > wrote: >> >> > Why not Use?! >> >> The Go team felt LLVM was too large and slow to meet their performance >> goals. >> > -- 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.
Re: [go-nuts] Go Compiler How Work?!
Tanks you. please also answer my first question. Last Version of Go Compiler doing Generate `ASM Code` and next Linker... and make final binary output file for they platform? On Saturday, December 16, 2017 at 3:17:31 AM UTC+3:30, Gianguido Sorà wrote: > > No, Go doesn't use LLVM. > > Il 16 dic 2017 00:45, "Compiler" <erfang...@gmail.com > ha > scritto: > >> Last Version of Go Compiler doing Generate `ASM Code` and next Linker... >> and final binary output file? >> >> >> Go Compiler is use LLVM/IR? >> >> >> go1.4/doc/go_faq.html : >> >> We considered using LLVM for gc but we felt it was too large >> and >> slow to meet our performance goals. >> >> >> >> On Wednesday, December 13, 2017 at 10:57:55 PM UTC+3:30, Bruno >> Albuquerque wrote: >>> >>> Go 1.4.2 compiler and linker code for x86-64. >>> >>> https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/ >>> https://go.googlesource.com/go/+/go1.4.2/src/cmd/6l/ >>> <https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/> >>> >>> >>> >>> On Wed, Dec 13, 2017 at 11:16 AM Compiler <erfang...@gmail.com> wrote: >>> >>>> please show me code of compiler , linker of go1.4.(Based on C) >>>> >>>> https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz >>>> >>>> >>>> On Wednesday, December 13, 2017 at 10:39:24 PM UTC+3:30, Bruno >>>> Albuquerque wrote: >>>> >>>>> 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 <erfang...@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...@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...@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...@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.
Re: [go-nuts] Go Compiler How Work?!
Why not Use?! This not more Easy? Google Team/Co at RustLang is using LLVM. On Saturday, December 16, 2017 at 3:17:31 AM UTC+3:30, Gianguido Sorà wrote: > > No, Go doesn't use LLVM. > > Il 16 dic 2017 00:45, "Compiler" <erfang...@gmail.com > ha > scritto: > >> Last Version of Go Compiler doing Generate `ASM Code` and next Linker... >> and final binary output file? >> >> >> Go Compiler is use LLVM/IR? >> >> >> go1.4/doc/go_faq.html : >> >> We considered using LLVM for gc but we felt it was too large >> and >> slow to meet our performance goals. >> >> >> >> On Wednesday, December 13, 2017 at 10:57:55 PM UTC+3:30, Bruno >> Albuquerque wrote: >>> >>> Go 1.4.2 compiler and linker code for x86-64. >>> >>> https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/ >>> https://go.googlesource.com/go/+/go1.4.2/src/cmd/6l/ >>> <https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/> >>> >>> >>> >>> On Wed, Dec 13, 2017 at 11:16 AM Compiler <erfang...@gmail.com> wrote: >>> >>>> please show me code of compiler , linker of go1.4.(Based on C) >>>> >>>> https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz >>>> >>>> >>>> On Wednesday, December 13, 2017 at 10:39:24 PM UTC+3:30, Bruno >>>> Albuquerque wrote: >>>> >>>>> 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 <erfang...@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...@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...@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...@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.
Re: [go-nuts] Go Compiler How Work?!
Last Version of Go Compiler doing Generate `ASM Code` and next Linker... and final binary output file? Go Compiler is use LLVM/IR? go1.4/doc/go_faq.html : We considered using LLVM for gc but we felt it was too large and slow to meet our performance goals. On Wednesday, December 13, 2017 at 10:57:55 PM UTC+3:30, Bruno Albuquerque wrote: > > Go 1.4.2 compiler and linker code for x86-64. > > https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/ > https://go.googlesource.com/go/+/go1.4.2/src/cmd/6l/ > <https://go.googlesource.com/go/+/go1.4.2/src/cmd/6c/> > > > > On Wed, Dec 13, 2017 at 11:16 AM Compiler <erfang...@gmail.com > > wrote: > >> please show me code of compiler , linker of go1.4.(Based on C) >> >> https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz >> >> >> On Wednesday, December 13, 2017 at 10:39:24 PM UTC+3:30, Bruno >> Albuquerque wrote: >> >>> 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 <erfang...@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...@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...@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.
[go-nuts] Re: Go Compiler How Work?!
tanks you. i not found complate book pdf file. you not have file?! On Wednesday, December 13, 2017 at 11:22:50 PM UTC+3:30, David Chase wrote: > > I think one of the best references to this is "BCPL: The Language and Its > Compiler". > It is shorter than the Dragon Book, accessible, historical, and very well > written. > I think you can find the PDF online (maybe, not sure). > > > On Tuesday, December 12, 2017 at 4:03:08 PM UTC-5, Compiler wrote: >> >> Hello, >> Go Compiler How Work at Last Version of GoLang?! >> i mean Go Compiler , Not GoLang. >> >> at the last version of golang. go compiler , generate c code and compile >> using gcc?! >> >> >> >> >> >> -- 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.
Re: [go-nuts] Go Compiler How Work?!
please show me code of compiler , linker of go1.4.(Based on C) https://storage.googleapis.com/golang/go1.4-bootstrap-20170531.tar.gz On Wednesday, December 13, 2017 at 10:39:24 PM UTC+3:30, Bruno Albuquerque wrote: > > 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 <erfang...@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...@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.
Re: [go-nuts] Go Compiler How Work?!
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.
Re: [go-nuts] Go Compiler How Work?!
Machine Code?! please show me github link source file then at they is generate sample binary... at GOLANG sources. On Wednesday, December 13, 2017 at 8:48:30 PM UTC+3:30, Andy Balholm wrote: > > No, the Go compiler doesn’t actually generate ASM. It generates machine > code. So it doesn’t need the help of another compiler or assembler. > > Andy > > On Dec 13, 2017, at 9:00 AM, Compiler <erfang...@gmail.com > > wrote: > > i am undrestand compiler steps. > only have problem in code generation step. > so best way is this then compiler generate code is ASM. > GOLANG also generate ASM. > > yeah? > > On Wednesday, December 13, 2017 at 8:27:41 PM UTC+3:30, Bruno Albuquerque > wrote: >> >> It directly generates a binary suitable for the target platform, yes. >> Again, you do not need a C compiler to compile a Go program unless you are >> using CGO. >> > > -- > 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...@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.
Re: [go-nuts] Re: Go Compiler How Work?!
i am undrestand compiler steps. only have problem in code generation step. so best way is this then compiler generate code is ASM. GOLANG also generate ASM. yeah? On Wednesday, December 13, 2017 at 8:27:41 PM UTC+3:30, Bruno Albuquerque wrote: > > It directly generates a binary suitable for the target platform, yes. > Again, you do not need a C compiler to compile a Go program unless you are > using CGO. > -- 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.
Re: [go-nuts] Re: Go Compiler How Work?!
please answer this. On Wednesday, December 13, 2017 at 4:30:52 PM UTC+3:30, Compiler wrote: > > are you sure GoCompiler/GoLang generate ASM code for build executable file > from .go? > -- 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.
