Am 11.09.2011 19:44, schrieb Lin Rongrong: > How much recommended --max-allocs-per-node with 4GB RAM? >
I cannot give an recommendation that way. It's always a compilation time vs. code size trade-off. With 4GB of RAM you'll start swapping - depending on the file being compiled - at about 2000000. However, once register allocation becomes provably optimal there's no further increase in run-time, no matter, how high you set --max-allocs-per-node. This happens for simple function, like the dhrystone benchmark: http://www.colecovision.eu/stuff/dhrystone.pdf Here's a large applications, the Contiki OS: http://www.colecovision.eu/stuff/contiki.pdf During development, you'll want a low value, such as the default 3000. However, when you're doing the final release and have time to let sdcc run overnight, you might want to set it to something high to get some extra optimization. Philipp ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Sdcc-user mailing list Sdcc-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sdcc-user
