----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://reviews.gem5.org/r/2492/#review5570 -----------------------------------------------------------
Ship it! src/mem/packet.hh <http://reviews.gem5.org/r/2492/#comment4993> Would it make sense to have an internal 'const' flag that we assert is cleared when calling the non-const getPtr() accessors? That could even be enabled optionally only for debug builds if desired. - Steve Reinhardt On Nov. 16, 2014, 10:14 p.m., Andreas Hansson wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > http://reviews.gem5.org/r/2492/ > ----------------------------------------------------------- > > (Updated Nov. 16, 2014, 10:14 p.m.) > > > Review request for Default. > > > Repository: gem5 > > > Description > ------- > > Changeset 10542:6cbdd036f4b9 > --------------------------- > mem: Use const pointers for port proxy write functions > > This patch changes the various write functions in the port proxies > to use const pointers for all sources (similar to how memcpy works). > > The one unfortunate aspect is the need for a const_cast in the packet, > to avoid having to juggle a const and a non-const data pointer. This > design decision can always be re-evaluated at a later stage. > > > Diffs > ----- > > src/mem/fs_translating_port_proxy.hh 1a9e235cab09 > src/mem/fs_translating_port_proxy.cc 1a9e235cab09 > src/mem/packet.hh 1a9e235cab09 > src/mem/port_proxy.hh 1a9e235cab09 > src/mem/port_proxy.cc 1a9e235cab09 > src/mem/se_translating_port_proxy.hh 1a9e235cab09 > src/mem/se_translating_port_proxy.cc 1a9e235cab09 > > Diff: http://reviews.gem5.org/r/2492/diff/ > > > Testing > ------- > > > Thanks, > > Andreas Hansson > > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
