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
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>
*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 compile
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-h
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
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
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
y 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 `
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 us
/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
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
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.googl
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.
>
: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 p
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 diffe
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:
>
#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
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
>
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
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
wr
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:
>>
>>
h 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 >
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
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 to
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 mi
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.
>
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:
>
&g
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
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,
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:
>
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
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 doe
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 su
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
"g
34 matches
Mail list logo
