mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Weinehall <tao@acc.umu.se>
To: "J . A . Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: gcc-3.0.2 and 2.4.14-pre1
Date: Fri, 26 Oct 2001 03:48:34 +0200	[thread overview]
Message-ID: <20011026034833.H25701@khan.acc.umu.se> (raw)
In-Reply-To: <20011026010432.A1536@werewolf.able.es>
In-Reply-To: <20011026010432.A1536@werewolf.able.es>; from jamagallon@able.es on Fri, Oct 26, 2001 at 01:04:32AM +0200

On Fri, Oct 26, 2001 at 01:04:32AM +0200, J . A . Magallon wrote:
> Hi.
> 
> Results of building with 3.0.2
> - It works
> - Kernel Sizes:
> 	903449 Oct 26 00:38 vmlinuz-2.4.14-pre1-beo			(2.96)
> 	864599 Oct 26 00:25 vmlinuz-2.4.14-pre1-beo.old		(3.0.2)

Aren't these figures swapped in some way? I find it hard to believe
that 2.96 would produce the 40k bigger kernel.

> - Modules Sizes:
> 	2750    /lib/modules/2.4.14-pre1-beo
> 	2758    /lib/modules/2.4.14-pre1-beo.org
> 	werewolf:/lib/modules# modprobe -l | wc -l
>    	  71
> 
> So it looks like the code is not bigger (modules) but some data structure
> in main kernel...

Quite likely due to the 16 bytes alignment that takes place (AFAIK).


/David
  _                                                                 _
 // David Weinehall <tao@acc.umu.se> /> Northern lights wander      \\
//  Project MCA Linux hacker        //  Dance across the winter sky //
\>  http://www.acc.umu.se/~tao/    </   Full colour fire           </

  reply	other threads:[~2001-10-26  1:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 23:04 J . A . Magallon
2001-10-26  1:48 ` David Weinehall [this message]
2001-10-26  3:44   ` The Doctor What
2001-10-26  8:05     ` J . A . Magallon

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=20011026034833.H25701@khan.acc.umu.se \
    --to=tao@acc.umu.se \
    --cc=jamagallon@able.es \
    --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®