Port: Make getAddrRanges const

This patch makes getAddrRanges const throughout the code base. There
is no reason why it should not be, and making it const prevents adding
any unintentional side-effects.
This commit is contained in:
Andreas Hansson
2012-07-09 12:35:34 -04:00
parent 830391cad9
commit 46d9adb68c
35 changed files with 57 additions and 54 deletions

View File

@@ -44,9 +44,10 @@ const uint8_t CommandNack = 0xfe;
const uint8_t BatSuccessful = 0xaa;
AddrRangeList
X86ISA::I8042::getAddrRanges()
X86ISA::I8042::getAddrRanges() const
{
AddrRangeList ranges;
// TODO: Are these really supposed to be a single byte and not 4?
ranges.push_back(RangeSize(dataPort, 1));
ranges.push_back(RangeSize(commandPort, 1));
return ranges;

View File

@@ -255,7 +255,7 @@ class I8042 : public BasicPioDevice
commandByte.keyboardFullInt = 1;
}
AddrRangeList getAddrRanges();
AddrRangeList getAddrRanges() const;
Tick read(PacketPtr pkt);

View File

@@ -101,7 +101,7 @@ class I82094AA : public PioDevice, public IntDev
Tick read(PacketPtr pkt);
Tick write(PacketPtr pkt);
AddrRangeList getAddrRanges()
AddrRangeList getAddrRanges() const
{
AddrRangeList ranges;
ranges.push_back(RangeEx(pioAddr, pioAddr + 4));
@@ -109,7 +109,7 @@ class I82094AA : public PioDevice, public IntDev
return ranges;
}
AddrRangeList getIntAddrRange()
AddrRangeList getIntAddrRange() const
{
AddrRangeList ranges;
ranges.push_back(RangeEx(x86InterruptAddress(initialApicId, 0),

View File

@@ -74,7 +74,7 @@ class IntDev
{
}
AddrRangeList getAddrRanges()
AddrRangeList getAddrRanges() const
{
return device->getIntAddrRange();
}
@@ -152,7 +152,7 @@ class IntDev
}
virtual AddrRangeList
getIntAddrRange()
getIntAddrRange() const
{
panic("intAddrRange not implemented.\n");
}