From: Jakub Jelinek <jakub@redhat.com>
To: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Dave Jones <davej@suse.de>
Subject: Re: Some functions are not inlined by gcc 3.2, resulting code is ugly
Date: Sun, 3 Nov 2002 10:37:10 -0500 [thread overview]
Message-ID: <20021103103710.D10988@devserv.devel.redhat.com> (raw)
In-Reply-To: <200211031322.gA3DMTp28125@Port.imtp.ilyichevsk.odessa.ua>; from vda@port.imtp.ilyichevsk.odessa.ua on Sun, Nov 03, 2002 at 04:14:26PM -0200
On Sun, Nov 03, 2002 at 04:14:26PM -0200, Denis Vlasenko wrote:
> Here is the cure: force_inline will guarantee inlining.
>
> To use _only_ with functions which meant to be almost
> optimized away to nothing but are large and gcc might decide
> they are _too_ large for inlining.
Well, you can as well bump -finline-limit, like -finline-limit=2000.
The default is too low for kernel code (and glibc too).
Jakub
next prev parent reply other threads:[~2002-11-03 15:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-03 16:17 Some functions are not inlined by gcc 3.2, resulting code is ugly Denis Vlasenko
2002-11-03 16:17 ` Jussi Laako
2002-11-04 0:17 ` Denis Vlasenko
2002-11-03 21:28 ` Jussi Laako
2002-11-04 16:00 ` Denis Vlasenko
2002-11-03 18:14 ` Denis Vlasenko
2002-11-03 15:23 ` Martin J. Bligh
2002-11-04 0:23 ` Denis Vlasenko
2002-11-03 15:37 ` Jakub Jelinek [this message]
2002-11-03 16:21 ` Alan Cox
2002-11-04 0:20 ` Denis Vlasenko
2002-11-03 20:28 ` Alan Cox
2002-11-04 16:08 ` Denis Vlasenko
2002-11-13 1:28 ` J.A. Magallón
2002-11-13 11:54 ` Denis Vlasenko
2002-11-13 12:48 ` Denis Vlasenko
2002-11-04 1:21 ` Robert Love
2002-11-04 13:41 ` Alan Cox
2002-11-04 22:44 ` Werner Almesberger
2002-11-04 16:04 ` Denis Vlasenko
2002-11-04 11:39 ` Jakub Jelinek
2002-11-13 0:10 ` J.A. Magallón
2002-11-13 12:04 ` Denis Vlasenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021103103710.D10988@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=vda@port.imtp.ilyichevsk.odessa.ua \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.