Messages in this thread | | | Date | Fri, 9 Jul 2004 08:24:03 +0200 | From | Arjan van de Ven <> | Subject | Re: GCC 3.4 and broken inlining. |
| |
On Fri, Jul 09, 2004 at 08:08:21AM +1000, Nigel Cunningham wrote: > Hi. > > On Fri, 2004-07-09 at 07:09, Arjan van de Ven wrote: > > the problem I've seen is that when gcc doesn't honor normal inline, it will > > often error out if you always inline.... > > I'm open to removing the < 4 but as jakub said, 3.4 is quit good at honoring > > normal inline, and when it doesn't there often is a strong reason..... > > I'm busy for the next couple of days, but if you want, I'll make > allyesconfig next week and go through fixing the compilation errors so > that the < 4 can be removed. Rearranging code so that inline functions > are defined before they're called or not declared inline if they can't > always be inlined seems to me to be the right thing to do. (Feel free to > say I'm wrong!).
one thing to note is that you also need to monitor stack usage then :) inlining somewhat blows up stack usage so do monitor it... [unhandled content-type:application/pgp-signature] | |