From: Werner Almesberger <wa@almesberger.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Robert Love <rml@tech9.net>, Jakub Jelinek <jakub@redhat.com>,
Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dave Jones <davej@suse.de>
Subject: Re: Some functions are not inlined by gcc 3.2, resulting code is ugly
Date: Mon, 4 Nov 2002 19:44:46 -0300 [thread overview]
Message-ID: <20021104194446.B1407@almesberger.net> (raw)
In-Reply-To: <1036417267.1106.36.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Mon, Nov 04, 2002 at 01:41:07PM +0000
Alan Cox wrote:
> gcc actually appears to know about that case for static functions.
Hmm. gcc 3.1 inlines functions even without being marked "inline"
when using -O3 or higher. It doesn't seem to special-case plain
"static", or even single-use "static".
Is gcc 3.2 better at this ?
-falways-inline-static-singletons would be kind of nice to have.
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2002-11-04 22:38 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
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 [this message]
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=20021104194446.B1407@almesberger.net \
--to=wa@almesberger.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@suse.de \
--cc=jakub@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox