This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug go/61877] [5 Regression]: reflect: cannot use []string as type string in Call
- From: "ian at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Fri, 03 Oct 2014 15:52:11 +0000
- Subject: [Bug go/61877] [5 Regression]: reflect: cannot use []string as type string in Call
- Auto-submitted: auto-generated
- References: <bug-61877-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61877
--- Comment #11 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Fri Oct 3 15:51:38 2014
New Revision: 215859
URL: https://gcc.gnu.org/viewcvs?rev=215859&root=gcc&view=rev
Log:
PR go/61877
refect: fix direct call of variadic method value
As reported in bug https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61877
gcc mainline has regressed in this. This CL adds the tests proposed
for the main Go repository:
https://codereview.appspot.com/151280043/
https://codereview.appspot.com/152060043/
restores the code from the amd64/386 path that makes this work and
was lost when the Go 1.3 stdlib was merged and changes the FFI path
to call into the same helper code as the amd64/386 path.
I've only tested this on amd64 but I did test a version that was
patched to unconditionally take the FFI path.
Modified:
trunk/libgo/go/reflect/all_test.go
trunk/libgo/go/reflect/makefunc.go