Re: [go-nuts] About Go Compiler!

...you might also want to read the papers about META II. This was memorably inspired work from 1965 that is still marvelous. http://www.ibm-1401.info/Meta-II-schorre.pdf On Sun, Feb 18, 2018 at 5:46 PM, Pierpaolo Bernardi wrote: > On Mon, Feb 19, 2018 at 1:44 AM, Compiler wrote: > > Performance

Re: [go-nuts] About Go Compiler!

On Mon, Feb 19, 2018 at 1:44 AM, Compiler wrote: > Performance of C with Optimize not better of Go at more time?! > so why re-write golang in go? Because a lot of people, obviously including Go implementors, think that Go is a better language than C for writing a compiler. Performance of the gen

Re: [go-nuts] About Go Compiler!

I recommend watching this presentation from Russ Cox about why the Go team decided to rewrite the compiler from C to Go. https://www.youtube.com/watch?v=QIE5nV5fDwA On Monday, 19 February 2018 11:44:23 UTC+11, Compiler wrote: > > Performance of C with Optimize not better of Go at more time?! >

Re: [go-nuts] About Go Compiler!

At the core of this is the simple fact that you have to start somewhere. The founding Go team had experience (UNIX, B, C, Plan 9, Pic, Blit, GNU C/C++, ...) and well-understood code on hand from prior work (assembler, compilers, and a linker that all worked together). Also, it is dangerous to buil

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, C

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 > > > On Monday, Februa

Re: [go-nuts] About Go Compiler!

*bootstrapping* is the technique for producing a self-compiling 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.wikipedi

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 securit

Re: [go-nuts] About Go Compiler!

much better! i suggest Google searches about bootstrapping, self-hosting, and security. On Sun, Feb 18, 2018 at 3:59 PM, Compiler wrote: > I have some experience in writing lexer,parser,interpreter,optimize. > I've also worked generate output code(example one language to another). > > currently

Re: [go-nuts] About Go Compiler!

If you want to learn more about the Go compiler then you must stop living in the past. Go 1.4 is _dead_. The current compiler is written in pure go and you can find the sources here https://github.com/golang/go/tree/master/src/cmd/compile/internal We cannot help you use the old Go 1.4 c compile

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 tryin

Re: [go-nuts] About Go Compiler!

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

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 .

Re: [go-nuts] About Go Compiler!

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 unsub

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

Re: [go-nuts] About Go Compiler!

On Monday, 19 February 2018 10:42:12 UTC+11, Compiler wrote: > > Assembly?! > but not exist many `.asm` files at source. > By tradition assembly files have .s and .S extensions > Also, I had already asked ... > Already asked what? It might be easier if you give more background to the _probl

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

Re: [go-nuts] About Go Compiler!

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’

Re: [go-nuts] About Go Compiler!

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 th

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 onl

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: >> >> >

Re: [go-nuts] About Go Compiler!

yes, up to Go 1.4, part of the go runtime was compiled using a c compiler which derived from the plan 9 c compilers. In fact, the c frontend and the go frontend shared the same code generation backends. On Monday, 19 February 2018 10:31:35 UTC+11, Compiler wrote: > > mean all `.c` file in /src/

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 Goo

Re: [go-nuts] About Go Compiler!

> 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...@

Re: [go-nuts] About Go Compiler!

> what files require the c compiler? The c files in the go 1.4 distribution. -- 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...@googlegroup

Re: [go-nuts] About Go Compiler!

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 beca

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

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 r

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 conta

Re: [go-nuts] About Go Compiler!

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 y

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 > wrote: > > #Question > > > > What is the difference between using the following two files? > > > > /go

Re: [go-nuts] About Go Compiler!

On Sun, Feb 18, 2018 at 9:23 AM, Compiler 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 > /g