This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: inlining default
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Jason Merrill <jason at redhat dot com>, Neil Booth <neil at daikokuya dot demon dot co dot uk>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 12 Dec 2001 23:41:31 -0500
- Subject: Re: inlining default
>>>>> Mark Mitchell writes:
>> It seems that Neil's 2001-11-15 changes to option parsing had a side
>> effect of turning on tree inlining at -O0 for C and C++ unless suppressed
>> with -fno-inline, because we now set flag_tree_inline from flag_no_inline
>> before setting flag_no_inline from optimize. Is this what we want? I
>> would prefer to leave it off by default with -O0, but many compilers turn
>> it on unless specifically disabled. What do other people think?
Mark> I think we should leave it off at -O0. I can't see a compelling
Mark> reason to change our historical practice.
Without inlining a -O0, GCC fundamentally uses a different source
stream with and without optimization. This makes debugging at -O0 more
difficult.
David