Michael Hudson-Doyle d25c3eadea cmd/compile: do not generate tail calls when dynamic linking on ppc64le ... When a wrapper method calls the real implementation, it's not possible to use a tail call when dynamic linking on ppc64le. The bad scenario is when a local call is made to the wrapper: the wrapper will call the implementation, which might be in a different module and so set the TOC to the appropriate value for that module. But if it returns directly to the wrapper's caller, nothing will reset it to the correct value for that function. Change-Id: Icebf24c9a2a0a9a7c2bce6bd6f1358657284fb10 Reviewed-on: https://go-review.googlesource.com/23468 Reviewed-by: Ian Lance Taylor <iant@golang.org> Run-TryBot: Michael Hudson-Doyle <michael.hudson@canonical.com> TryBot-Result: Gobot Gobot <gobot@golang.org>		2016-06-02 02:34:01 +00:00
..
dep2	cmd/link: always read type data for dynimport symbols	2016-05-04 07:13:01 +00:00
dep3	cmd/link: always read type data for dynimport symbols	2016-05-04 07:13:01 +00:00
depBase	cmd/compile: do not generate tail calls when dynamic linking on ppc64le	2016-06-02 02:34:01 +00:00
exe	cmd/link: always read type data for dynimport symbols	2016-05-04 07:13:01 +00:00
exe2	cmd/compile: do not generate tail calls when dynamic linking on ppc64le	2016-06-02 02:34:01 +00:00
exe3	cmd/link: always read type data for dynimport symbols	2016-05-04 07:13:01 +00:00
execgo	cmd/link: when reading symbols from a shared library, allow duplicates when they are both in bss	2015-06-16 22:33:36 +00:00
explicit	cmd/link: allow symbols from .a files to override those from .so files	2016-01-20 19:53:53 +00:00
implicit	cmd/link: allow symbols from .a files to override those from .so files	2016-01-20 19:53:53 +00:00
implicitcmd	cmd/link: allow symbols from .a files to override those from .so files	2016-01-20 19:53:53 +00:00
trivial	…