Currently go program 1.3, 1.4 and 1.5 has a really different compilation performance, the later has about 4x slower than the former. How to trace the go compiler execution? something like this:note: valgrind + calgrind doesn't work (tutorial) valgrind --tool=callgrind /usr/bin/go build==26982== Callgrind, a call-graph generating cache profiler==26982== Copyright (C) 2002-2015, and GNU GPL'd, by Josef Weidendorfer et al.==26982== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info==26982== Command: /usr/bin/go build==26982== ==26982== For interactive control, run 'callgrind_control -h'.fatal error: rt_sigaction failureruntime stack:runtime.throw(0x9a2bf0, 0x14)        /usr/lib/go/src/runtime/panic.go:527 +0x90runtime.setsig(0xc800000040, 0x4e40d0, 0x1)        /usr/lib/go/src/runtime/os1_linux.go:297 +0x197runtime.initsig()        /usr/lib/go/src/runtime/signal1_unix.go:67 +0x13druntime.mstart1()        /usr/lib/go/src/runtime/proc1.go:717 +0xc9runtime.mstart()        /usr/lib/go/src/runtime/proc1.go:691 +0x72goroutine 1 [runnable]:runtime.main()        /usr/lib/go/src/runtime/proc.go:28runtime.goexit()        /usr/lib/go/src/runtime/asm_amd64.s:1696 +0x1goroutine 17 [syscall, locked to thread]:runtime.goexit()        /usr/lib/go/src/runtime/asm_amd64.s:1696 +0x1==26982== ==26982== Events    : Ir==26982== Collected : 851285==26982== ==26982== I   refs:      851,285
How to trace program execution?
performance