Review Board 2.0.15


Power: Change bitfield name to avoid conflicts with range_map

Review Request #1109 - Created March 21, 2012 and submitted - Latest diff uploaded

Information
Andreas Hansson
gem5
default
Reviewers
Default
Power: Change bitfield name to avoid conflicts with range_map

This patch changes the name of a bitfield from W to W_FIELD to avoid
clashes with W being used as a class (typename) in the templatized
range_map. It also changes L to L_FIELD to avoid future problems. The
problem manifestes itself when the CPU includes a header that in turn
includes range_map.hh. The relevant parts of the decoder are updated.
util/regress all passing (disregarding t1000 and eio)