From: Steve Reinhardt <stever@eecs.umich.edu>
Date: Sat, 19 May 2007 05:20:58 +0000 (-0400)
Subject: Oops... some places in C++ explicitly ask for a "functional"
X-Git-Tag: m5_2.0_beta4~396^2~5
X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=aa5b595f39b778d0f6532b40761ca5d6275c2aa0;p=gem5.git

Oops... some places in C++ explicitly ask for a "functional"
port.  It would be better to move this to python IMO but for
now I'll stick in a compatibility hack.

--HG--
extra : convert_revision : a81a29cbd43becd0e485559eb7b2a31f7a0b082d
---

diff --git a/src/mem/physical.cc b/src/mem/physical.cc
index 2ca3f1c83..a49959e51 100644
--- a/src/mem/physical.cc
+++ b/src/mem/physical.cc
@@ -336,6 +336,13 @@ PhysicalMemory::doFunctionalAccess(PacketPtr pkt)
 Port *
 PhysicalMemory::getPort(const std::string &if_name, int idx)
 {
+    // Accept request for "functional" port for backwards compatibility
+    // with places where this function is called from C++.  I'd prefer
+    // to move all these into Python someday.
+    if (if_name == "functional") {
+        return new MemoryPort(csprintf("%s-functional", name()), this);
+    }
+
     if (if_name != "port") {
         panic("PhysicalMemory::getPort: unknown port %s requested", if_name);
     }