Date: Wed, 23 Jul 2003 10:14:58 -0700 (PDT) From: Nate Lawson <nate@root.org> To: Garance A Drosihn <drosih@rpi.edu> Cc: src-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/kern init_main.c kern_malloc.c md5c.c subr_autoconf.c subr_mbuf.c subr_prf.c tty_subr.c vfs_cluster.c vfs_subr.c Message-ID: <20030723101220.B39567@root.org> In-Reply-To: <p05210685bb438fb2dcbb@[128.113.24.47]> References: <20030723003212.1606C2A8B2@canning.wemm.org> <p05210685bb438fb2dcbb@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Jul 2003, Garance A Drosihn wrote: > At 5:32 PM -0700 7/22/03, Peter Wemm wrote: > >Take the i386 interrupt vector code. Thats an example where > >it is massively inlined. Having a non-inlined function that > >does all the calculations and bit shifting is much smaller > >in code size, but slower at runtime. > > If I understand this discussion correctly, then the previous > version of gcc (in freebsd-current) was NOT inlining these > sections event though we thought it was. Might we expect some > performance improvements now that we know to force gcc to > inline the functions? Excellent troll. :) [FYI, the long-winded discussion underway is whether the many cases of inlining actually do have any performance gain. Not all requests for inline were rejected, only those for "large" functions where gcc's idea of large is also being debated.] -Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030723101220.B39567>