[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] 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] Tools for developing Go compiler/ Go code from SSA

he linker? * I see stacksplit code in cmd/internal/obj/ directory which is invoked during compileSSA() in gc/pgen.go. Thanks a lot! Mohit On Fri, Jul 5, 2019 at 11:32 AM Keith Randall wrote: > > > On Fri, Jul 5, 2019 at 2:05 PM Mohit Verma wrote: > >> Thanks Keith, Ian.

[go-nuts] Tools for developing Go compiler/ Go code from SSA

Hi All, I am trying to change the ssa phase of Go compiler to do extra work during memory stores. For example whenever there is a memory store, I want to make a function call to one of my Go packages instead of the store. So, far I have some working changes and I can see the new SSA nodes when I

Re: [go-nuts] Persistent memory support for Go

t memory accessible to Go developers. Thanks! Mohit From: Robert Engels Date: Wednesday, April 3, 2019 at 4:00 PM To: Jerrin Shaji George Cc: "golang-nuts@googlegroups.com" , Mohit Verma , Pratap Subrahmanyam , Rajesh Venkatasubramanian Subject: Re: [go-nuts] Persistent memory

Re: [go-nuts] Debugging & breakpoints in Go compiler source code

: > On Fri, Mar 8, 2019 at 4:23 PM Mohit Verma wrote: > > > > I was looking to see how the golang compiler works, and wanted to step > in to the compilation process to see what happens. I am looking at the > standard Go compiler in src/cmd/compile from https://github.com/golang/g

[go-nuts] Debugging & breakpoints in Go compiler source code

Hi All, I was looking to see how the golang compiler works, and wanted to step in to the compilation process to see what happens. I am looking at the standard Go compiler in src/cmd/compile from https://github.com/golang/go. When I try to run the compilation process with gdb, I see I can put