aboutsummaryrefslogtreecommitdiff
path: root/gcc
diff options
context:
space:
mode:
authorIan Lance Taylor <ian@gcc.gnu.org>2014-10-03 15:51:38 +0000
committerIan Lance Taylor <ian@gcc.gnu.org>2014-10-03 15:51:38 +0000
commit22806403ec9dff3f819ac87298aca28a7e795cb0 (patch)
treeb092d9b0ceaf4ff19e48ba6cb48bf54842aac96c /gcc
parentacbe08d242491a93e90957116dffa81c9f91ee11 (diff)
downloadgcc-22806403ec9dff3f819ac87298aca28a7e795cb0.zip
gcc-22806403ec9dff3f819ac87298aca28a7e795cb0.tar.gz
gcc-22806403ec9dff3f819ac87298aca28a7e795cb0.tar.bz2
re PR go/61877 (reflect: cannot use []string as type string in Call)
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. From-SVN: r215859
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions