On Wed, Aug 25, 2010 at 4:56 PM, chromatic <[email protected]> wrote: > On Tuesday 24 August 2010 at 10:14, plobsing wrote: > >> Author: plobsing >> Date: Tue Aug 24 17:14:54 2010 >> New Revision: 48634 >> URL: https://trac.parrot.org/parrot/changeset/48634 >> >> Log: >> inline undocumented, used-once static functions > > Shouldn't a decent optimizing compiler inline used-once static functions? (I > know there's often a size limit for this, but before we manually inline such > functions I want to make sure we do so for good reasons.)
Optimization was not at all the intent of this commit. These functions were used in vtables with single-line bodies calling these functions. They served no purpose except to add a level of indirection while source diving and an extra line or two to backtraces on unoptimized builds. > -- c > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev > _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
