compiler: don't export any functions with special names
authorIan Lance Taylor <ian@gcc.gnu.org>
Fri, 19 Oct 2018 19:43:47 +0000 (19:43 +0000)
committerIan Lance Taylor <ian@gcc.gnu.org>
Fri, 19 Oct 2018 19:43:47 +0000 (19:43 +0000)
commit12d5ebf9630364515229268e48c04cffd069dd32
tree2317ee528d8f155674d9a4d87cf3324a9d39392e
parent3146c60f16558e7eae1039ba6c937f75413ce4f9
compiler: don't export any functions with special names

    This keeps init functions from appearing in the export data.  Checking
    for special names in general means that we don't need to check
    specifically for nested functions or thunks, which have special names.

    Reviewed-on: https://go-review.googlesource.com/c/143237

From-SVN: r265321
gcc/go/gofrontend/MERGE
gcc/go/gofrontend/export.cc