public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Chris Wedgwood <cw@f00f.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"David S. Miller" <davem@redhat.com>,
	vandrove@vc.cvut.cz, torvalds@transmeta.com,
	garzik@havoc.gtf.org, linux-kernel@vger.kernel.org,
	paulus@samba.org, davidm@hpl.hp.com, ralf@gnu.org
Subject: Re: [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does
Date: Fri, 01 Feb 2002 19:01:56 -0800	[thread overview]
Message-ID: <3C5B56A4.B762948F@zip.com.au> (raw)
In-Reply-To: <20020131.145904.41634460.davem@redhat.com> <E16WQYs-0003Ux-00@the-village.bc.nu>, <E16WQYs-0003Ux-00@the-village.bc.nu> <20020202021242.GA6770@tapu.f00f.org>

Chris Wedgwood wrote:
> 
> On Thu, Jan 31, 2002 at 11:24:10PM +0000, Alan Cox wrote:
> 
>     Because 100 4K drivers suddenly becomes 0.5Mb. There are those of
>     us trying to stuff Linux into embedded devices who if anything
>     want more configuration options not people taking stuff out.
> 
> Well, I'm more or less in agreement here, especially when working with
> small embedded devices which have a few (say 16 or 32) MB of RAM for
> EVERYTHING, kernel, userspace AND filesystems.
> 
> However, I wonder if we can't have the linker remove unnecessary and
> unreferences objects, functions and variables?

We can.  Graham Stoney had all this going against 2.2.  See

http://www.google.com/search?q=stoney+ffunction-sections&hl=en&start=10&sa=N
http://www.cs.helsinki.fi/linux/linux-kernel/Year-2000/2000-29/0415.html

>     What I'd much rather see if this is an issue is:
> 
>     bool        'Do you want to customise for a very small system'
> 
> _IF_ the linker can remove things, it would simplify this too --- we
> could if a few important places produce code slightly differently to
> favour speed over size and not reference various things.  Also, the
> above option would turn-off inlining as that seems to makie quite a
> difference at times (BTW, I'm not sure about this, but it seems gcc
> and C99 don't agree with static/extern inline semantics?)

The kernel doesn't link when you compile with -fno-inline because of all
the `extern inline' qualifiers.  These need to be converted to `static
inline'.    Jim Houston has a script which does this.  See

	http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.3/0888.html

It would be rather good if we could get that script run across the
tree - no-inline has its uses at times.

-

  reply	other threads:[~2002-02-02  3:02 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-31 20:27 crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does not Petr Vandrovec
2002-01-31 20:31 ` Jeff Garzik
2002-01-31 22:53   ` [PATCH] " Petr Vandrovec
2002-01-31 22:59     ` David S. Miller
2002-01-31 23:08       ` Jeff Garzik
2002-01-31 23:43         ` David Lang
2002-01-31 23:24       ` [PATCH] Re: crc32 and lib.a (was Re: [PATCH] nbd in 2.5.3 does Alan Cox
2002-01-31 23:21         ` Arnaldo Carvalho de Melo
2002-02-02 16:32           ` Denis Vlasenko
2002-02-02 12:57             ` Jens Axboe
2002-02-02 13:16               ` arjan
2002-02-02 13:52                 ` Jens Axboe
2002-02-03 11:37             ` David Woodhouse
2002-01-31 23:43         ` Jeff Garzik
2002-01-31 23:45         ` David S. Miller
2002-02-01  0:32           ` Alan Cox
2002-02-01 10:07           ` Horst von Brand
2002-02-01 10:28             ` Keith Owens
2002-02-01 11:03               ` David S. Miller
2002-02-01 11:25                 ` Keith Owens
2002-02-01 14:56                   ` Jeff Garzik
2002-02-01  8:14         ` David Woodhouse
2002-02-02  2:12         ` Chris Wedgwood
2002-02-02  3:01           ` Andrew Morton [this message]
2002-02-02  7:30             ` Chris Wedgwood
2002-02-02  7:42               ` Daniel Jacobowitz
2002-02-02  8:08                 ` Jeff Garzik
2002-02-02 19:20                   ` Daniel Jacobowitz
2002-02-02  8:06               ` Jeff Garzik
2002-02-02  8:08               ` Keith Owens
2002-02-02  8:40                 ` David Woodhouse
2002-02-02  8:59                   ` Keith Owens
2002-02-02  9:14                     ` David Woodhouse
2002-02-03  4:14         ` Eric W. Biederman
2002-02-03  7:01           ` Ralf Baechle
2002-02-03  9:13             ` Chris Wedgwood
2002-02-03 12:16             ` David Woodhouse
2002-02-03 12:33               ` Chris Wedgwood
2002-02-03 12:47               ` David Woodhouse
2002-02-03 13:40             ` Alan Cox
     [not found] <20020131.162549.74750188.davem@redhat.com>
2002-02-01  0:42 ` Alan Cox
2002-02-01  0:30   ` David S. Miller
2002-02-01  3:46     ` Jeff Garzik
2002-02-01  4:25       ` David S. Miller
2002-02-01  4:48         ` Jeff Garzik
2002-02-01  5:59           ` David S. Miller
2002-02-01  5:10         ` Keith Owens
2002-02-01  5:12           ` Jeff Garzik
2002-02-01  5:18             ` Keith Owens
2002-02-01 13:42               ` Horst von Brand
2002-02-03 23:34                 ` Keith Owens
2002-02-04 20:14                   ` Horst von Brand
2002-02-01  6:01           ` David S. Miller
2002-02-01  6:11             ` Keith Owens
2002-02-01  6:26               ` David S. Miller
2002-02-01  6:43                 ` Keith Owens
2002-02-01 15:03                 ` Alan Cox
2002-02-01 14:55                   ` Jeff Garzik
2002-02-01 15:12                     ` Petr Vandrovec
2002-02-01 16:08                     ` David Woodhouse
2002-02-04 13:24                     ` Horst von Brand
2002-02-05  7:51                       ` Jeff Garzik
2002-02-01  4:18     ` H. Peter Anvin
2002-02-01  4:35       ` Jeff Garzik
2002-02-01 15:19     ` Alan Cox
2002-02-01 19:37     ` Rob Landley
2002-02-01 19:50       ` Jeff Garzik

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=3C5B56A4.B762948F@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=davem@redhat.com \
    --cc=davidm@hpl.hp.com \
    --cc=garzik@havoc.gtf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=ralf@gnu.org \
    --cc=torvalds@transmeta.com \
    --cc=vandrove@vc.cvut.cz \
    /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