Thanks. The example that shows the difference is at the issue.
```
package main
import "fmt"
func main() {
nNeg := 10.0
fpr := 10.0
invNeg := 1 / nNeg
fpr = 1 - fpr*invNeg
fmt.Println(fpr)
}
```
And, yes, it looks like it could be constant propagation.
On Mon, Jan 13, 2020 at 5:45 PM Dan Kortschak wrote:
> Thanks for linking this here.
>
> One thing that I did not follow up at the issue; why do we see the FMA
> being applied when the value is a slice element, but not when it's a
> single float64 value?
>
>
I'd have to see an example to be
Thanks for linking this here.
One thing that I did not follow up at the issue; why do we see the FMA
being applied when the value is a slice element, but not when it's a
single float64 value?
Second query, are there plans for adding FMA support to amd64 akin to
how it is on arm64?
Dan
On Mon,
Note: discussion at https://github.com/golang/go/issues/36536 . TL;DR fused
floating point multiply-add gives higher precision results.
On Sunday, January 12, 2020 at 8:19:54 PM UTC-8, kortschak wrote:
>
> I am going through failures that I see in Gonum tests when we build on
> arm64 (Travis
friends
looking for guidance on how to get an rsa.PublicKey from id_rsa.pub
seems like I can parse the id_rsa.pub contents and get a ssh.PublicKey but
how do I transform this into an rsa.PublicKey
i need the coersion in order to use other support services.
thanks for any pointers, srini
--
It can get expensive to do that. Instead of just a mark bit per object, and
a queue of pointers to mark, you need a mark bit per word and a queue of
ptr+len. You can also end up doing more than constant work per mark.
x := [10]*int{ ... 10 pointers ... }
a := x[:3:3]
b := x[7::]
x is now dead,
Ok. Thanks. I’ll play around with it a bit more. If it doesn't work out,
there’s always C code!
On Mon, Jan 13, 2020 at 2:03 AM Ian Lance Taylor wrote:
> On Sun, Jan 12, 2020 at 6:50 PM Anthony Adams
> wrote:
> >
> > Thanks again. That’s very helpful. It sounds like ARMv5 is still
> supported.
On Sat, Jan 11, 2020 at 4:43 AM wrote:
>> But there's one guarantee - the "dead" slice portion after
>> cap will not be scanned by the collector if no other live object uses
>> it.
>
>
> That's not correct. If there is a reference to an object, the entire object
> is live and is scanned,
Hi Gophers,
I have updated my list of Go interfaces for this new release:
http://sweetohm.net/article/go-interfaces.en.html
Enjoy!
Le jeu. 9 janv. 2020 à 23:16, Carlos Amedee a écrit :
> Hello gophers,
>
> We have just released Go versions 1.13.6 and 1.12.15, minor point releases.
>
> These
If you call through an interface, you get runtime, dynamic dispatch.
--
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
10 matches
Mail list logo
