On Sunday 19 February 2012 12:46:45 David White wrote: > Yes, at this point it'd be best to remove them.
All right; I have just removed the custom allocator and its support bits in the Wesnoth proper in r53125. I hope I didn't miss anything. > There are now many mature and high quality allocation libraries we could > choose from that most likely reduce fragmentation. For instance, Google's > allocator, Intel's allocator (shipping with Intel TBB) and jmalloc, used by > Firefox. I think that it'd be worth exploring these different allocators > and see if any of them offers significant performance improvements for > Wesnoth. (Actually doing something like this seems like a nice example of > an achievable GSoC project to me). I'm not sure whether this kind of tasks belongs to GSoC. I always thought (or maybe I was told so at some point) that the program was more about producing a substantial amount of lines of code for open-source software while being paid. Assuming other custom allocators are set up in a similar fashion, wouldn't this just require choosing the right library and doing a lot of benchmarking and regression testing work rather than actual programming? -- Regards Ignacio Riquelme Morelle <shadowmaster>
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
