> - There's some code protected by '#if FAST_ALLOC_DEBUG' that is intended to > help debug memory leaks using FastAlloc. I've used it once or twice, but I > kind of doubt that anyone else has, and I'm sure it's not as good as using > valgrind or probably several other malloc debug packages. It seems > particuarly ironic to have debug code in a module that is disabled in > m5.debug, so I propose getting rid of this. That would also let us get rid > of the FAST_ALLOC_DEBUG scons sticky var, so we'd be at a wash in terms of > sticky var count.
It's not unusable if you have FORCE_FAST_ALLOC, but if you don't think it's useful, then we can get rid of it. Nate _______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
