compiler: don't export any functions with special names
commit4a0fb313c2ac38ec7cbe0cb75015af74c0770639
authorian <ian@138bc75d-0d04-0410-961f-82ee72b054a4>
Fri, 19 Oct 2018 19:43:47 +0000 (19 19:43 +0000)
committerian <ian@138bc75d-0d04-0410-961f-82ee72b054a4>
Fri, 19 Oct 2018 19:43:47 +0000 (19 19:43 +0000)
tree2317ee528d8f155674d9a4d87cf3324a9d39392e
parentcd66715a19a498de4874b98634890024776810fb
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

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@265321 138bc75d-0d04-0410-961f-82ee72b054a4
gcc/go/gofrontend/MERGE
gcc/go/gofrontend/export.cc