This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Inlining (was: GCC 3.3 release criteria)
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Andi Kleen <ak at suse dot de>
- Cc: gcc at gcc dot gnu dot org
- Date: 26 Feb 2003 12:52:00 +0100
- Subject: Re: Inlining (was: GCC 3.3 release criteria)
- Organization: Integrable Solutions
- References: <F0B5E2D8-48EA-11D7-A0F6-00039390D9E0@apple.com.suse.lists.egcs><m3wujn90fs.fsf@uniton.integrable-solutions.net.suse.lists.egcs><20030226044029.A1163@kerberos.ncsl.nist.gov.suse.lists.egcs><m3isv78gp7.fsf@uniton.integrable-solutions.net.suse.lists.egcs><p73wujn6zn3.fsf@amdsimf.suse.de><m3smub6zdn.fsf@uniton.integrable-solutions.net><20030226114740.GA18775@wotan.suse.de>
Andi Kleen <ak at suse dot de> writes:
| > | forces -Werror -Winline
| >
| > Why so?
|
| always_inline errors when the function cannot get inlined.
Thanks for the education and your patience.
But then if -fobey-inline doesn't error then there is something about it?
Matt, what does happen when a function can't be inlined?
-- Gaby