From b911771f129c599c4f5a6f9b866d300c4fa42159 Mon Sep 17 00:00:00 2001 From: Matthew Dempsky Date: Mon, 8 Aug 2022 15:47:09 -0700 Subject: [PATCH] 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 Run-TryBot: Cuong Manh Le TryBot-Result: Gopher Robot Reviewed-by: Than McIntosh --- src/cmd/compile/internal/ir/fmt.go | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/src/cmd/compile/internal/ir/fmt.go b/src/cmd/compile/internal/ir/fmt.go index 760ae7df1e..5912438d09 100644 --- 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) -- 2.50.0