> > I don't know if you saw my email on one of the mailing lists related to this > that got into more detail, but the field being read is from an int added in > one of the M5 patches, so that should actually be pretty stable unless the > size of an int changed (does that ever happen?) or we change the patch > around. Basically it sticks the offset of some members of a structure into > ints that M5 can read out pretty easily, and maybe some other things I'm not > remembering off hand. I would guess the purpose of the patch in the first > place is to put those values somewhere we can have a bit more control over. > It might be a good idea to even change those to be a fixed size integer like > int32_t (which should be quite sufficient) that wouldn't depend on how big an > int ended up being. I'm not familiar with bfd, but if it is or has type data > for debugging purposes then that would make at least some of those ints > unnecessary. > > int won't change on Alpha ever. int32_t is better, but it doesn't matter too much. That is what bfd does, but it's a big library. Would be cool to figure it out some day.
Go for it. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
