| commit | ac17498a5eab9526cf34686e80cc52a4408b3f07 | |
| author | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 29 Apr 2015 22:40:07 +0000 (29 22:40 +0000) | ||
| committer | ian <ian@138bc75d-0d04-0410-961f-82ee72b054a4> | |
| Wed, 29 Apr 2015 22:40:07 +0000 (29 22:40 +0000) | ||
| tree | 32052a5b2324b3645095c963ed6bcc8b0b5bc8dd | treesnapshot (tar.gz zip) |
| parent | 1c9e2501dad960b4b049fde0979ae2d3b9bc542b | commitdiff |
compiler: Consider multi-result calls in escape analysis.
When building connection graphs between objects, the analysis
only handled calls of the form `call(...)` or `var := call(...)`.
Functions with multiple results being used e.g. `var, _ = call(...)`
were not analyzed, causing some escaping variables to be marked as
non-escaping.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@222598 138bc75d-0d04-0410-961f-82ee72b054a4
When building connection graphs between objects, the analysis
only handled calls of the form `call(...)` or `var := call(...)`.
Functions with multiple results being used e.g. `var, _ = call(...)`
were not analyzed, causing some escaping variables to be marked as
non-escaping.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@222598 138bc75d-0d04-0410-961f-82ee72b054a4
| gcc/go/gofrontend/escape.cc | diffblobblamehistory |