[go-nuts] Re: go1.10.windows-386.msi have securityalert in ESET

Likely a false positive from your antivirus. See: https://tip.golang.org/doc/faq#virus A. Il giorno martedì 20 marzo 2018 04:48:21 UTC+1, sa koji ha scritto: > > when install go1.10.windows-386.msi、eset do security alert. > does this have solved problem? > -- You received this message because

[go-nuts] Re: Go 1.9 Beta 2 is released

But if you have other numbers please share them, it'll certainly interesing to see them. Il giorno giovedì 29 giugno 2017 13:38:18 UTC+2, Parker Evans ha scritto: > > Congratulations on the Beta 2 release, pretty excited to test it out. > Lots of interesting updates! > > I did notice one thing

[go-nuts] Re: Go 1.9 Beta 2 is released

Unstripped "hello world"s are ~20% bigger on my Linux system too, but it seems like the loss is much smaller on real programs, e.g. see Brad comment here: https://github.com/golang/go/issues/6853#issuecomment-307155309 A. Il giorno giovedì 29 giugno 2017 13:38:18 UTC+2, Parker Evans ha

[go-nuts] Re: Dead link on page https://blog.golang.org/go-fmt-your-code

Thanks for the report. I opened https://github.com/golang/go/issues/19036 A. Il giorno venerdì 10 febbraio 2017 21:51:20 UTC+1, Константин Изюмов ha scritto: > > Please pay your attention on page https://blog.golang.org/go-fmt-your-code > with dead link under word "Vim plugin for Go", because

Re: [go-nuts] Go 1.7.5 and Go 1.8rc3 are released

A better link is this one, IMHO: github.com/golang/go/compare/go1.7.4...go1.7.5 the gerrit one shows uninteresting CLs too, like: [release-branch.go1.7] cmd/godoc: add perf subrepo while the github one doesn't Il giorno venerdì 27 gennaio 2017 15:58:20 UTC+1, Steven Hartland ha scritto: > >

Re: [go-nuts] Slow 64 bit integer division on amd64

If the div overflow, it will trigger and hardware exception. Il giorno giovedì 10 novembre 2016 15:01:06 UTC+1, ra...@cockroachlabs.com ha scritto: > > I don't understand. We are truncating the result to 32-bits either way. > What's the point of computing the entire 64-bits of the result just

Re: [go-nuts] Go 1.7.3 is released

It *wasn't* backported. Il giorno mercoledì 19 ottobre 2016 22:17:51 UTC+2, alb.do...@gmail.com ha scritto: > > The time failure is Issue 17276. I patched it on tip > but it was backported in 1.7 > > Il giorno mercoledì 19 ottobre 2016 22:10:42 UTC+2, Jan Mercl ha scritto: >> >> On Wed, Oct 19,

Re: [go-nuts] Go 1.7.3 is released

The time failure is Issue 17276. I patched it on tip but it was backported in 1.7 Il giorno mercoledì 19 ottobre 2016 22:10:42 UTC+2, Jan Mercl ha scritto: > > On Wed, Oct 19, 2016 at 9:45 PM Chris Broadfoot > wrote: > > > We have just released Go version 1.7.3, a minor point

[go-nuts] Re: High memory usage of math/big.putNat for web application

Does this happens on tip too? There was a recent CL that modified the code of the nat pool; see https://go-review.googlesource.com/#/c/30613/ exp. the "Eliminate allocation in divLarge nat pool" part. Il giorno sabato 15 ottobre 2016 16:28:01 UTC+2, Raffaele Di Fazio ha scritto: > > Hi, > I

[go-nuts] Re: Go API checker

At that point, the toolchain is already built. Just ignore that the API checker says. Il giorno venerdì 5 agosto 2016 18:37:33 UTC+2, stable.p...@gmail.com ha scritto: > > Hello, > > I have made some changes to a part of the go standard library. I am > testing these to see if they help me do

Re: [go-nuts] [ANN] primegen.go: Sieve of Atkin prime number generator

> Do you plan to include SSA for the x86 version as well? For an answer to this: yes, it seems like the plan is to port every supported architecture to SSA. It was discussed here: https://groups.google.com/d/msg/golang-dev/fSIl5Sbr4ek/10sgOsnDEAAJ Il giorno martedì 21 giugno 2016 03:39:41

[go-nuts] Re: [ANN] primegen.go: Sieve of Atkin prime number generator

> Current versions of golang are not as fast as GCC C/C++ optimized code by at least a factor of two This is, in general, not true at all: I've written numeric code as fast as C code compiled by GCC -O3 Il giorno martedì 14 giugno 2016 14:31:18 UTC+2, gordo...@gmail.com ha scritto: > > That's