cmd/compile/internal/ir: better dump for OLINKSYMOFFSET

When debugging IR that uses OLINKSYMOFFSET, you really need to know
what linksym it actually refers to.

Change-Id: I7f4775d040b50e36262f9f8b52d0fb112b7ed350
Reviewed-on: https://go-review.googlesource.com/c/go/+/422194
Reviewed-by: Cuong Manh Le <cuong.manhle.vn@gmail.com>
Run-TryBot: Cuong Manh Le <cuong.manhle.vn@gmail.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Than McIntosh <thanm@google.com>

diff --git a/src/cmd/compile/internal/ir/fmt.go b/src/cmd/compile/internal/ir/fmt.go
index 760ae7df1e4465b81c68be2015a900bcf03a3664..5912438d095a8632dae65872d590d658221cf252 100644 (file)
--- a/src/cmd/compile/internal/ir/fmt.go
+++ b/src/cmd/compile/internal/ir/fmt.go
@@ -1127,6 +1127,15 @@ func dumpNode(w io.Writer, n Node, depth int) {
                dumpNodeHeader(w, n)
                return
 
+       case OLINKSYMOFFSET:
+               n := n.(*LinksymOffsetExpr)
+               fmt.Fprintf(w, "%+v-%v", n.Op(), n.Linksym)
+               // Offset is almost always 0, so only print when it's interesting.
+               if n.Offset_ != 0 {
+                       fmt.Fprintf(w, "%+v", n.Offset_)
+               }
+               dumpNodeHeader(w, n)
+
        case OASOP:
                n := n.(*AssignOpStmt)
                fmt.Fprintf(w, "%+v-%+v", n.Op(), n.AsOp)