Linked by Tony Bourke on Thu 22nd Jan 2004 21:29 UTC
Permalink for comment
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
More News »
Sponsored Links



I don't think that's the sort of "optimization" the original poster was talking about, especially since the technique is entirely irrelevent to the benchmarks presented in the article.
Plus, what you are talking about is not so much optimization as it is getting rid of hacks that are no longer necessary because of a more permissive CPU architecture. Optimization takes general code and tunes it for a specific situation. What you are describing is actually the reverse --- taking code tuned for a specific situation (low-memory) and generalizing it.