From: johan.adolfsson@axis.com
To: "Adam J. Richter" <adam@yggdrasil.com>, <linux-kernel@vger.kernel.org>
Subject: Re: List of all-zero .data variables in linux-2.4.3 available
Date: Thu, 12 Apr 2001 16:44:48 +0200 [thread overview]
Message-ID: <070001c0c35f$201f3740$a8b270d5@homeip.net> (raw)
In-Reply-To: <200104121236.FAA03613@adam.yggdrasil.com>
Shouldn't a compiler be able to deal with this instead?
(Just a thought.)
/Johan
----- Original Message -----
From: Adam J. Richter <adam@yggdrasil.com>
To: <linux-kernel@vger.kernel.org>
Sent: Thursday, April 12, 2001 2:36 PM
Subject: List of all-zero .data variables in linux-2.4.3 available
> For anyone who is interested, I have produced a list of all
> of the .data variables that contain all zeroes and could be moved to
> .bss within the kernel and all of the modules (all of the modules
> that we build at Yggdrasil for x86, which is almost all). These
> are global or static variables that have been declared
>
> int foo = 0;
>
> instead of
>
> int foo; /* = 0 */
>
> The result is that the .o files are bigger than they have
> to be. The kernel memory image is not bigger, and gzip shrinks the
> runs of zeroes down to almost nothing, so it does not have a huge effect
> on bootable disks. Still, it would be nice to save the disk space of
> the approximately 75 kilobytes of zeroes and perhaps squeeze in another
> sector or two when building boot floppies.
>
> I have also included a copy of the program that I wrote to
> find these all-zero .data variables.
>
> The program and the output are FTPable from
> ftp://ftp.yggdrasil.com/private/adam/linux/zerovars/. Files with no
> all-zero .data variables are not included in the listing. If you maintain
> any code in the kernel, you might want to look at the output to see
> how your code stacks up.
>
> Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite
104
> adam@yggdrasil.com \ / San Jose, California
95129-1034
> +1 408 261-6630 | g g d r a s i l United States of America
> fax +1 408 261-6631 "Free Software For The Rest Of Us."
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-04-12 14:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-12 12:36 Adam J. Richter
2001-04-12 14:44 ` johan.adolfsson [this message]
2001-04-12 14:57 ` Russell King
2001-04-12 15:28 ` Richard B. Johnson
2001-04-12 19:52 ` Jeff Garzik
2001-04-12 19:01 Adam J. Richter
2001-04-12 19:14 ` Ulrich Drepper
2001-04-12 21:27 ` H. Peter Anvin
2001-04-12 19:29 Adam J. Richter
2001-04-12 19:40 ` Ulrich Drepper
2001-04-16 14:33 ` Pavel Machek
2001-04-12 19:50 Adam J. Richter
2001-04-12 20:04 Adam J. Richter
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='070001c0c35f$201f3740$a8b270d5@homeip.net' \
--to=johan.adolfsson@axis.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®