From: Pavel Machek <pavel@suse.cz>
To: Andi Kleen <ak@muc.de>
Cc: Anton Blanchard <anton@samba.org>,
torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Use __attribute__((malloc)) for gcc 3.2
Date: Wed, 2 Oct 2002 13:46:23 +0000 [thread overview]
Message-ID: <20021002134623.B61@toy.ucw.cz> (raw)
In-Reply-To: <20020930003121.GB2805@averell>; from ak@muc.de on Mon, Sep 30, 2002 at 02:31:21AM +0200
Hi!
> > > may be useful to prevent some awful code generation for those misguided
> > > folks who use -O3 (gcc often screws up the register allocation of a
> > > function completely when bigger functions are inlined).
> >
> > Could you also add an always inline? It would be useful for functions
> > like context_switch, where we require it to be inlined (otherwise it
> > falls outside scheduling_functions_{start,end}_here and wchan handling
> > fails).
>
> Ok. gcc supports it with __attribute__((always_inline))
>
> Suggestions for a name? alwaysinline would be a bit lengthy.
do_inline?
Pavel
--
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.
next prev parent reply other threads:[~2002-10-02 21:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 15:27 [PATCH] Use __attribute__((malloc)) for gcc 3.2 Andi Kleen
2002-09-29 16:24 ` Adrian Bunk
2002-09-29 17:26 ` Christoph Hellwig
2002-09-30 0:11 ` David S. Miller
2002-09-30 0:29 ` Andi Kleen
2002-09-29 20:01 ` Jakub Jelinek
2002-09-30 0:04 ` Andi Kleen
2002-10-07 10:05 ` Richard Henderson
2002-10-07 10:29 ` David S. Miller
2002-10-07 10:56 ` Andi Kleen
2002-10-07 11:07 ` Arjan van de Ven
2002-10-07 11:45 ` Richard Henderson
2002-10-07 12:27 ` Andi Kleen
2002-09-29 23:51 ` Anton Blanchard
2002-09-30 0:31 ` Andi Kleen
2002-09-30 1:07 ` Daniel Jacobowitz
2002-10-02 13:46 ` Pavel Machek [this message]
[not found] <20020929152731.GA10631@averell.suse.lists.linux.kernel>
[not found] ` <20020929182643.C8564@infradead.org.suse.lists.linux.kernel>
2002-09-29 19:09 ` Andi Kleen
2002-09-29 20:20 ` Adrian Bunk
2002-09-30 0:21 ` David S. Miller
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=20021002134623.B61@toy.ucw.cz \
--to=pavel@suse.cz \
--cc=ak@muc.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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;
as well as URLs for NNTP newsgroup(s).