Joel Reymont <joe...@gmail.com> wrote: > From Apple's guide to improving code locality [1], it's possible to get gprof > to output an [...] Ordering based on a ?closest is best? analysis of the > profiling > call graph. Calls that call each other frequently are placed close together.
A classic example of using tis optimization was the Multics "binder", which took a list of functions or libraries and made a new library, optionally making particular entry points unreachable. It was used for performance work by grouping mutually referencing functions together, so the linkages didn't require work by the runtime linker. Physical locality was a useful side-effect. It was also used to build what we'd now call a kind of subclassing, hiding the original class behind a new interface with the same signature. Similar to Solaris filter libraries. You could do the same thing with dtrace/prof data and a bit of selection on the inputs to the linker. --dave -- David Collier-Brown | Always do right. This will gratify Sun Microsystems, Toronto | some people and astonish the rest dav...@sun.com | -- Mark Twain cell: (647) 833-9377, home (416) 223-8968, bridge (877) 385-4099 code 506 9191# _______________________________________________ dtrace-discuss mailing list dtrace-discuss@opensolaris.org
