compiler: don't insert write barriers if we've seen errors
commitf4a156ff0dec09a0c84973af401c6c9ca89d5eab
authorian <ian@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 29 Jan 2018 20:58:23 +0000 (29 20:58 +0000)
committerian <ian@138bc75d-0d04-0410-961f-82ee72b054a4>
Mon, 29 Jan 2018 20:58:23 +0000 (29 20:58 +0000)
treecea9966958f939db1ea3448f9452e7a5c89bb6e4
parent81cc7d9c8b8e60e4a0e40351de5bfbdc04bb52b8
compiler: don't insert write barriers if we've seen errors

    The compiler skips the escape analysis pass if it has seen any errors.
    The write barrier pass, especially the check-escapes portion, relies
    on escape analysis running.  So don't run this pass if there have been
    any errors, as it may cause further unreliable error reports.

    Reviewed-on: https://go-review.googlesource.com/90575

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