From 1eac10b39f164c3010fe8fee2fed3269fa832967 Mon Sep 17 00:00:00 2001
From: Ian Lance Taylor <ian@gcc.gnu.org>
Date: Tue, 9 Jan 2018 17:21:01 +0000
Subject: compiler: use macro Unordered_map instead of std::unordered_map

    Per gcc/go/go-system.h, this is what it is supposed to be, to
    support wider platforms.

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

From-SVN: r256389
---
 gcc/go/gofrontend/escape.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'gcc/go/gofrontend/escape.cc')

diff --git a/gcc/go/gofrontend/escape.cc b/gcc/go/gofrontend/escape.cc
index 8706808..50878ff 100644
--- a/gcc/go/gofrontend/escape.cc
+++ b/gcc/go/gofrontend/escape.cc
@@ -858,7 +858,7 @@ Gogo::analyze_escape()
 
       // Propagate levels across each dst.  This is the flood phase.
       std::set<Node*> dsts = context->dsts();
-      std::unordered_map<Node*, int> escapes;
+      Unordered_map(Node*, int) escapes;
       for (std::set<Node*>::iterator n = dsts.begin();
            n != dsts.end();
            ++n)
-- 
cgit v1.1