[go-nuts] garbage collector forced to run every two minutes

Hi, I was wondering what problem *gcTriggerTime* is supposed to solve? Why does the language need to force the GC every two minutes if it did not run? Thanks in advance -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this

Re: [go-nuts] Re: How to build gollvm on arm platform

On Wed, Sep 18, 2019 at 7:09 PM joe mcguckin wrote: > > What's the advantage of an LLVM based compiler. GC seems to be fast and makes > OK code. Is the llvm toolchain that much better? It's always a good idea to have multiple compilers, as it helps ensure that the language is defined by a spec

Re: [go-nuts] Where to find documentation for old Golang releases

On Wed, Sep 18, 2019 at 7:06 PM Leo R wrote: > > Hi ALL, > For several reasons I have to stay with Go-1.12.x. But after Go-1.13 has been > released I cannot find 1.12 documentation online any longer. Official Golang > portal https://golang.org only provides documentation for the latest release.

Re: [go-nuts] Re: How to build gollvm on arm platform

Ian, What's the advantage of an LLVM based compiler. GC seems to be fast and makes OK code. Is the llvm toolchain that much better? joe On Wednesday, September 18, 2019 at 5:08:16 PM UTC-7, Ian Lance Taylor wrote: > > On Wed, Sep 18, 2019 at 5:02 PM joe mcguckin > > wrote: > > > > What's

[go-nuts] Where to find documentation for old Golang releases

Hi ALL, For several reasons I have to stay with Go-1.12.x. But after Go-1.13 has been released I cannot find 1.12 documentation online any longer. Official Golang portal https://golang.org only provides documentation for the latest release. Are there any online resources that have older

[go-nuts] Re: SSA-able and canSSA meaning in Go compiler's SSA backend?

On Wednesday, September 18, 2019 at 1:50:27 PM UTC-7, Mohit Verma wrote: > > Hi All, > > I was reading Go compiler's SSA backend code at > cmd/compile/internal/gc/ssa/go > > & > cmd/compile/internal/ssa >

Re: [go-nuts] Re: How to build gollvm on arm platform

On Wed, Sep 18, 2019 at 5:02 PM joe mcguckin wrote: > > What's the difference between the standard GO compiler and GOLLVM? The standard Go compiler, also called the gc compiler, is written entirely in Go. GoLLVM is written in C++ and uses the LLVM backend. > I thought there was an llvm based

[go-nuts] Re: x/net/Listen behaviours

Is listener() a blocking operation? -- 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. To view this discussion on the web

[go-nuts] Re: How to build gollvm on arm platform

What's the difference between the standard GO compiler and GOLLVM? I thought there was an llvm based compiler that was abandoned? Thanks, Joe -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving

[go-nuts] go.mod changes on each build, -mod=readonly can never work

Hi, I've got a modules problem, and I'm not sure yet whether it's operator error or something worthy of a bug report. In short, I have a build where go.mod oscillates between two states build by build. The first build changes it one way, the next build changes it back. If I try the build

[go-nuts] SSA-able and canSSA meaning in Go compiler's SSA backend?

Hi All, I was reading Go compiler's SSA backend code at cmd/compile/internal/gc/ssa/go & cmd/compile/internal/ssa , and I keep on seeing some code

Re: [go-nuts] Clarification on unsafe conversion between string <-> []byte

On Wed, Sep 18, 2019 at 2:42 AM Francis wrote: > > I am looking at the correct way to convert from a byte slice to a string and > back with no allocations. All very unsafe. > > I think these two cases are fairly symmetrical. So to simplify the discussion > below I will only talk about

[go-nuts] Re: request for feedback: another websocket server implementation

You're absolutely right. Disregard my comment. On Wednesday, September 18, 2019 at 1:10:38 PM UTC-4, Jochen Voss wrote: > > Dear Ilia, > > Thank you for your comment. In my mind, Read and Write are made for > streaming data, whereas a websocket connection transports messages. How > would I

[go-nuts] Issue

[image: error.gif] I was working on a project (name of project is not allow), however in my project i want to show 3d model or my website. My website written in go. Aframe i'm using. When my website load 3d model it's show warning and my model is not visible on my website. Please help me

[go-nuts] Re: request for feedback: another websocket server implementation

Dear Ilia, Thank you for your comment. In my mind, Read and Write are made for streaming data, whereas a websocket connection transports messages. How would I handle message types and message boundaries when using the io.Reader and io.Writer interfaces? (I do try to implement these

[go-nuts] Re: request for feedback: another websocket server implementation

Dear T L, Thanks for this. I was aware of implementations number 1 and 4 (and I think I like my own better than these), but I didn't spot numbers 2 and 3. I'll have a look at these, too. Many thanks, Jochen On Wednesday, 18 September 2019 14:27:17 UTC+1, T L wrote: > > Just for reference.

Re: [go-nuts] Re: Package-to-package bindings and package-scope variables

Hi all, @clement auger I've looked at your links and they're all great, though the three last ones spoiled me a part of what I still have to do in my own project ;) Appart from that, I've already (quite successfully it seems) developped the part of the program that is supposed to take care of

Re: [go-nuts] ls: unsupported SSLv2 handshake received

As I understand it, the issue isn’t actually about SSLv2 itself. It’s that clients that support SSLv2 use an old handshake format. In that handshake, they can advertise support for SSLv3 and maybe even TLS 1. So if crypto/tls added support for the handshake but not the rest of SSLv2, they could

Re: [go-nuts] How to build gollvm on arm platform

Thanks for the update. BlockLIRBuilder sounds like the right way to go, and your plan to add unit tests SGTM. Agree that we'll need to thread through the arch/callingConv into the unit testing framework, let me know if I can help with that. Cheers, Than On Wed, Sep 18, 2019 at 3:46 AM eric

[go-nuts] Re: request for feedback: another websocket server implementation

You should try to make Conn implement io.Reader and io.Writer On Tuesday, September 17, 2019 at 6:29:08 PM UTC-4, Jochen Voss wrote: > > Dear all, > > Because I wanted to learn about the websocket protocol, I have implemented > a websocket server in Go: > > code:

[go-nuts] Re: request for feedback: another websocket server implementation

Just for reference. Here are other Go websocket implementations: * Gorilla WebSocket https://github.com/gorilla/websocket * https://github.com/nhooyr/websocket * https://github.com/gobwas/ws * x/net/websocket https://godoc.org/golang.org/x/net/websocket On Tuesday, September 17, 2019 at 6:29:08

[go-nuts] Clarification on unsafe conversion between string <-> []byte

I am looking at the correct way to convert from a byte slice to a string and back with no allocations. All very unsafe. I think these two cases are fairly symmetrical. So to simplify the discussion below I will only talk about converting from a string to []byte. func StringToBytes(s string) (b

[go-nuts] Re: ls: unsupported SSLv2 handshake received

Prabhash Rathore once said: > Looking at comment, it seems Golang does not support SSLv2 and SSLV3. The crypto/tls package can support SSLv3 if you set tls.Config.MinVersion to tls.VersionSSL30, but only as a server. > I am reaching out to see if there is anyway possible to add support for >

Re: [go-nuts] How to build gollvm on arm platform

Hi Than, I think here should be the right place to handle this case, and I have corrected the code. I should use BlockLIRBuilder instead of BinstructionLIRBuilder. I have implemented a prototype of the code and at present everything is normal. Next I will start writing some unit test cases.