Currently Ruby does dynamically set the size of the bitsets and assigns bitsets of different lengths to each other. However, I don't think that is really necessary. Rather it is just convenient because Ruby uses the machineCount function to set the bitset size and that function is not available during construction. You can certainly reorganize SLICC to set the max size at construction, but it will take a little effort.
If someone is willing to replace the current Ruby Set implementation with stl::bitset, I'll volunteer to make the necessary SLICC changes. Brad > -----Original Message----- > From: m5-dev-boun...@m5sim.org [mailto:m5-dev-boun...@m5sim.org] > On Behalf Of Korey Sewell > Sent: Wednesday, April 06, 2011 9:13 PM > To: M5 Developer List > Subject: Re: [m5-dev] Running Ruby w/32 Cores > > Hi Ali, > My only problem with stl::bitset here is that the "Set" type from Ruby seems > to have the option to be resizable (through the overloaded assignment > operator). That's what I meant by arbitrary length. > > In practice, I'm not sure if they ever assign sets of different lengths to > each > other (causing resizing), but if they do, then that would suggest that using > the stl::bitset isnt a straightforward thing (definitely "do-able" though, > just > not plug/play). > > If the resizing is just a unused "feature" of Ruby, then I would suggest we > switch to bitset. > > -- > - Korey > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
