Ruby: Use MasterPort base-class pointers where possible
authorAndreas Hansson <andreas.hansson@arm.com>
Sat, 14 Apr 2012 09:46:59 +0000 (05:46 -0400)
committerAndreas Hansson <andreas.hansson@arm.com>
Sat, 14 Apr 2012 09:46:59 +0000 (05:46 -0400)
commit14edc6013d8d62782d58536214c669e12c64da37
tree639d9ed2d37086bad6eb9576a4cfcc02729860e5
parent750f33a90194f3f827ef887fb7e151235e61c919
Ruby: Use MasterPort base-class pointers where possible

This patch simplifies future patches by changing the pointer type used
in a number of the Ruby testers to use MasterPort instead of using a
derived CpuPort class. There is no reason for using the more
specialised pointers, and there is no longer a need to do any casting.

With the latest changes to the tester, organising ports as readers and
writes, things got a bit more complicated, and the "type" now had to
be removed to be able to fall back to using MasterPort rather than
CpuPort.
src/cpu/testers/directedtest/InvalidateGenerator.cc
src/cpu/testers/directedtest/RubyDirectedTester.hh
src/cpu/testers/directedtest/SeriesRequestGenerator.cc
src/cpu/testers/rubytest/Check.cc
src/cpu/testers/rubytest/RubyTester.cc
src/cpu/testers/rubytest/RubyTester.hh