mirror of
https://github.com/golang/go
synced 2024-11-19 16:14:49 -07:00
e8cda0a6c9
It causes a crash because of the unexpected XDOT operation. It's not needed, since we will run ComputeAddrTaken() on function instantiations after stenciling. And it's not always correct, since we may not be able to distinguish between a array and a slice, if a type is dependent on a type param. However, we do need to call ComputeAddrTaken on instantiations created during inlining, since that is after the main ComputeAddrTaken pass. Fixes #49659 Change-Id: I0bb610cf11f14e4aa9068f6ca2a012337b069c79 Reviewed-on: https://go-review.googlesource.com/c/go/+/365214 Trust: Dan Scales <danscales@google.com> Run-TryBot: Dan Scales <danscales@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Keith Randall <khr@golang.org>
29 lines
506 B
Go
29 lines
506 B
Go
// run -gcflags=-G=3
|
|
|
|
// Copyright 2021 The Go Authors. All rights reserved.
|
|
// Use of this source code is governed by a BSD-style
|
|
// license that can be found in the LICENSE file.
|
|
|
|
// Testing that AddrTaken logic doesn't cause problems for function instantiations
|
|
|
|
package main
|
|
|
|
type A[T interface{ []int | [5]int }] struct {
|
|
val T
|
|
}
|
|
|
|
//go:noinline
|
|
func (a A[T]) F() {
|
|
_ = &a.val[2]
|
|
}
|
|
|
|
func main() {
|
|
var x A[[]int]
|
|
x.val = make([]int, 4)
|
|
_ = &x.val[3]
|
|
x.F()
|
|
var y A[[5]int]
|
|
_ = &y.val[3]
|
|
y.F()
|
|
}
|