ruby,gpu-compute: bugfix for GPU_VIPER* protocols

12db50c895 changed how directory mapping works, but it seems to have
broken the VIPER variants of the GPU protocols. The fix involves
declaring the function in the related '.sm' files.

Change-Id: I116980d42a4aa648369058b529c9f8d9693eb894
Reviewed-on: https://gem5-review.googlesource.com/8521
Reviewed-by: Anthony Gutierrez <anthony.gutierrez@amd.com>
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Maintainer: Anthony Gutierrez <anthony.gutierrez@amd.com>

src/mem/protocol/GPU_VIPER-TCC.sm

@@ -126,6 +126,7 @@ machine(MachineType:TCC, "TCC Cache")
   void wakeUpAllBuffers();
   void wakeUpBuffers(Addr a);
 
+  MachineID mapAddressToMachine(Addr addr, MachineType mtype);
 
   // FUNCTION DEFINITIONS
   Tick clockEdge();

src/mem/protocol/GPU_VIPER_Region-TCC.sm

@@ -131,6 +131,7 @@ machine(MachineType:TCC, "TCC Cache")
   void wakeUpAllBuffers();
   void wakeUpBuffers(Addr a);
 
+  MachineID mapAddressToMachine(Addr addr, MachineType mtype);
 
   // FUNCTION DEFINITIONS
 

src/mem/protocol/MOESI_AMD_Base-Region-dir.sm

@@ -210,6 +210,8 @@ machine(MachineType:Directory, "AMD_Base-like protocol")
   void wakeUpBuffers(Addr a);
   Cycles curCycle();
 
+  MachineID mapAddressToMachine(Addr addr, MachineType mtype);
+
   Entry getDirectoryEntry(Addr addr), return_by_pointer="yes" {
     Entry dir_entry := static_cast(Entry, "pointer", directory.lookup(addr));