[go-nuts] Re: Testing changes to Go SSA?

> Or is there a general testsuite that language developers use to test > compiler changes? I see this: > https://github.com/Byron/benchmarksgame-cvs-mirror but I am not sure if > this is the right place to look at. > That github site seems very out-of-date.

Re: [go-nuts] Re: Will the number of OS threads spawned by a golang process never decrease?

On Thu, Sep 19, 2019 at 10:25 AM Varun V wrote: > > I tried to post this message before I came across > https://github.com/golang/go/issues/14592. I couldn't post it successfully > then. I don't know why this message is posted now As it says at

[go-nuts] Re: Testing changes to Go SSA?

In addition to the tests you saw, there are a bunch of tests in test/codegen that makes sure specific sequences of instructions are or are not generated. Tests for specific issues that have been fixed are in test/fixedbugs. Generally the whole test suite is one giant compiler test. Run all.bash

[go-nuts] Re: Testing changes to Go SSA?

In addition to the tests you saw, there are a bunch of tests in test/codegen that makes sure specific sequences of instructions are or are not generated. Tests for specific issues that have been fixed are in test/fixedbugs. Generally the whole test suite is one giant compiler test. Run all.bash

[go-nuts] Re: Testing changes to Go SSA?

In addition to the tests you saw, there are a bunch of tests in test/codegen that makes sure specific sequences of instructions are or are not generated. Tests for specific issues that have been fixed are in test/fixedbugs. Generally the whole test suite is one giant compiler test. Run all.bash

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

I’ve filed this as #34417, at https://github.com/golang/go/issues/34417 > On Sep 19, 2019, at 09:52, Russ Selph wrote: > > Thanks for the hints. I'll try to reproduce from the tip branch before > filing a bug. > >> On Sep 19, 2019, at 09:34, t

[go-nuts] Testing changes to Go SSA?

Hi, I added a new pass to Go SSA for experimental purposes. Is there a testsuite to make sure Go's SSA backend works as intended? I do see some test files in ssa/ and gc/ directory but they seem to be testing specific cases in the code. For example, Are there 1. tests that would test the

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

Thanks for the tips. I'll try to reproduce from the tip branch before filing a bug. On Thursday, September 19, 2019 at 9:34:38 AM UTC-7, t hepudds wrote: > > Hello Russ, > > Usually, if you are not modifying your code, I think go.mod should be > stable across repeated identical invocations of

[go-nuts] Re: Will the number of OS threads spawned by a golang process never decrease?

I tried to post this message before I came across https://github.com/golang/go/issues/14592. I couldn't post it successfully then. I don't know why this message is posted now On Thursday, September 19, 2019 at 8:56:39 PM UTC+5:30, Varun V wrote: > > Consider a golang program running on a system

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

Thanks for the hints. I'll try to reproduce from the tip branch before filing a bug. > On Sep 19, 2019, at 09:34, t hepudds wrote: > > Hello Russ, > > Usually, if you are not modifying your code, I think go.mod should be stable > across repeated identical invocations of something like 'go

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

Hello Russ, Usually, if you are not modifying your code, I think go.mod should be stable across repeated identical invocations of something like 'go build' or 'go install'. I think there were a similar sounding set of bugs fixed for Go 1.13, but sounds like you are seeing this with Go 1.13.

[go-nuts] Will the number of OS threads spawned by a golang process never decrease?

Consider a golang program running on a system with GOMAXPROCS value 10. Initially OS has spawned 10 threads for execution. Due to blocking system calls, OS spawns 30 more threads resulting in 40 OS threads attached to the process.After all the blocked system calls return, then will the process

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

> Here is a link to a talk from a Go developer about adding SSA to the compiler That Go developer is the one who answered OP's question :) On Thursday, 19 September 2019 17:55:33 UTC+5:30, howar...@gmail.com wrote: > > Read this wiki page to understand what the goal is: >

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

Read this wiki page to understand what the goal is: https://en.wikipedia.org/wiki/Static_single_assignment_form Basically, SSA-form allows certain optimizations that are harder without it, but SSA is also itself hard to apply. SSA examples are often posed in the form of simple variables, but

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

Read this wiki page to understand what the goal is: https://en.wikipedia.org/wiki/Static_single_assignment_form Basically, SSA-form allows certain optimizations that are harder without it, but SSA is also itself hard to apply. SSA examples are often posed in the form of simple variables, but

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

Read this wiki page to understand what the goal is: https://en.wikipedia.org/wiki/Static_single_assignment_form Basically, SSA-form allows certain optimizations that are harder without it, but SSA is also itself hard to apply. SSA examples are often posed in the form of simple variables, but