Re: [go-nuts] Go Compiler How Work?!

On Saturday, 16 December 2017 10:21:15 UTC+1, Compiler wrote: > > 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?! > This is re

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

Re: [go-nuts] Go Compiler How Work?!

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.

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?! >> >>

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 o

Re: [go-nuts] Go Compiler How Work?!

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

Re: [go-nuts] Go Compiler How Work?!

Just to be clear, I wasn’t being serious. But then again, I’m starting to think that you aren’t being serious either. -- 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 ema

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 yo

Re: [go-nuts] Go Compiler How Work?!

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

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 si

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

Re: [go-nuts] Go Compiler How Work?!

> 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

Re: [go-nuts] Go Compiler How Work?!

If for use golang/compiler no need any tools and another compiler. and if not generate ASM code. so go compiler generate what?! On Saturday, December 16, 2017 at 3:30:14 AM UTC+3:30, andrey mirtchovski wrote: > > > Last Version of Go Compiler doing Generate `ASM Code` and next Linker... > and ma

Re: [go-nuts] Go Compiler How Work?!

> Last Version of Go Compiler doing Generate `ASM Code` and next Linker... and > make final binary output file for they platform? The modern Go compilers (https://golang.org/cmd/compile/, gccgo) do not generate "ASM Code" unless an appropriate flag is presented to them. For the "compile" tool (go

Re: [go-nuts] Go Compiler How Work?!

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 rece

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 di

Re: [go-nuts] Go Compiler How Work?!

> 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+unsubsc

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" > ha > scritto: > >> Last Version of Go Compiler doing Generate `ASM Code` a

Re: [go-nuts] Go Compiler How Work?!

No, Go doesn't use LLVM. Il 16 dic 2017 00:45, "Compiler" 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

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

Re: [go-nuts] Go Compiler How Work?!

The code is inside the file you referenced. That is a tar ball of the source of the bootstrap 1.4.2 compiler. -- 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 go

Re: [go-nuts] Go Compiler How Work?!

Oh, and the generic compiler frontend: https://go.googlesource.com/go/+/go1.4.2/src/cmd/gc/ On Wed, Dec 13, 2017 at 11:27 AM 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.

Re: [go-nuts] Go Compiler How Work?!

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/ On Wed, Dec 13, 2017 at 11:16 AM Compiler wrote: > please show me code of compiler , l

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

Re: [go-nuts] Go Compiler How Work?!

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 tryi

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 opera

Re: [go-nuts] Go Compiler How Work?!

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 t

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 t

Re: [go-nuts] Go Compiler How Work?!

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 wrote: > > i am undrestand compiler steps. > only have problem in code generation step. > so best way is this

[go-nuts] Go Compiler How Work?!

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 fro