LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Jesse Barnes <jbarnes@engr.sgi.com>,
davidm@hpl.hp.com, hch@infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fixing sendfile on 64bit architectures
Date: Thu, 20 May 2004 15:32:02 -0700 [thread overview]
Message-ID: <16557.12770.576039.306562@napali.hpl.hp.com> (raw)
In-Reply-To: <20040520152510.02de52a1.akpm@osdl.org>
>>>>> On Thu, 20 May 2004 15:25:10 -0700, Andrew Morton <akpm@osdl.org> said:
Andrew> Jesse Barnes <jbarnes@engr.sgi.com> wrote:
>> On Thursday, May 20, 2004 5:56 pm, Andrew Morton wrote: > An
>> alternative might be to remove all the ifdefs, build with >
>> -ffunction-sections and let the linker drop any unreferenced
>> code...
>> That would probably be even more confusing than the #ifdefs. At
>> least with those you know that you need to check whether the
>> current code will be called...
Andrew> Me no understand Jesse.
Andrew> Removing the ifdefs and letting the linker do the job has
Andrew> the advantage that the compiler gets to check more code for
Andrew> you.
I think he meant that it's easier to see who (what platform) is
relying on the code.
Another disadvantage of -ffunction-sections is that the compiler won't
be able to do proper inlining. There are several cases where you
have:
static
do_the_work ()
{
...
}
asmlinkage long
sys_one_variant ()
{
do_the_work(some args...);
}
asmlinkage long
sys_other_variant ()
{
do_the_work(other args...);
}
If only one variant is needed, GCC 3.4 will automatically inline
"do_the_work()" (since there is only one call-site), which is exactly
what you want. You won't get that with -ffunction-sections.
--david
next prev parent reply other threads:[~2004-05-20 22:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <26879984$108499340940abaf81679ba6.07529629@config22.schlund.de>
[not found] ` <16556.19979.951743.994128@napali.hpl.hp.com>
[not found] ` <20040519234106.52b6db78.davem@redhat.com>
[not found] ` <16556.65456.624986.552865@napali.hpl.hp.com>
[not found] ` <20040520120645.3accf048.akpm@osdl.org>
2004-05-20 19:26 ` David Mosberger
2004-05-20 19:35 ` Christoph Hellwig
2004-05-20 20:17 ` David Mosberger
2004-05-20 21:56 ` Andrew Morton
2004-05-20 22:00 ` David Mosberger
2004-05-20 22:09 ` David Mosberger
2004-05-20 23:30 ` Andrew Morton
2004-05-20 23:44 ` David Mosberger
2004-05-21 0:17 ` Spam: " Andrew Morton
2004-05-21 0:25 ` David Mosberger
2004-05-20 22:10 ` Jesse Barnes
2004-05-20 22:25 ` Andrew Morton
2004-05-20 22:32 ` David Mosberger [this message]
2004-05-20 22:33 ` Jesse Barnes
[not found] <1Y1yE-4Lz-7@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-9@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-11@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-13@gated-at.bofh.it>
[not found] ` <1Y1yF-4Lz-15@gated-at.bofh.it>
[not found] ` <1Y1yE-4Lz-5@gated-at.bofh.it>
[not found] ` <1Y1yJ-4Lz-37@gated-at.bofh.it>
[not found] ` <1Y2l5-5rr-5@gated-at.bofh.it>
[not found] ` <1Y3Ki-6x6-35@gated-at.bofh.it>
2004-05-21 9:01 ` Andi Kleen
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=16557.12770.576039.306562@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=hch@infradead.org \
--cc=jbarnes@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--subject='Re: [PATCH] fixing sendfile on 64bit architectures' \
/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
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).