All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael-lists@free-electrons.com>
To: "Simon Holm Thøgersen" <odie@cs.aau.dk>
Cc: Matt Mackall <mpm@selenic.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org, Linux-tiny@selenic.com
Subject: Re: [PATCH] x86 (Linux Tiny): configure out support for some	processors
Date: Sat, 09 Feb 2008 10:29:02 +0100	[thread overview]
Message-ID: <47AD725E.6050903@free-electrons.com> (raw)
In-Reply-To: <1202545817.6722.24.camel@odie.local>

On 02/09/2008 09:30 AM, Simon Holm Thøgersen wrote:
> The build of my currently running kernel for my laptop has
> $ size -t amd.o cyrix.o centaur.o transmeta.o intel.o nexgen.o umc.o
>    text	   data	    bss	    dec	    hex	filename
>    2809	    316	      0	   3125	    c35	amd.o
>    2387	    856	      0	   3243	    cab	cyrix.o
>    1514	    312	      0	   1826	    722	centaur.o
>    1279	    312	      0	   1591	    637	transmeta.o
>    1783	    316	      0	   2099	    833	intel.o
>     126	    312	      0	    438	    1b6	nexgen.o
>      41	    312	      0	    353	    161	umc.o
>    9939	   2736	      0	  12675	   3183	(TOTALS)
>
> That is without optimize for size compilation, with that set I get
> $ size -t amd.o cyrix.o centaur.o transmeta.o intel.o nexgen.o umc.o
>    text	   data	    bss	    dec	    hex	filename
>    2300	    316	      0	   2616	    a38	amd.o
>    2132	    820	      0	   2952	    b88	cyrix.o
>    1325	    312	      0	   1637	    665	centaur.o
>    1151	    312	      0	   1463	    5b7	transmeta.o
>    1575	    316	      0	   1891	    763	intel.o
>     107	    312	      0	    419	    1a3	nexgen.o
>      41	    312	      0	    353	    161	umc.o
>    8631	   2700	      0	  11331	   2c43	(TOTALS)
>
> I don't think the code changes in the patch do much with respect to
> size.
>   
Thanks for this report. Don't you think it's still useful to save up to
12 K of code that you don't use if you just have an Intel processor (for
example)?

Cheers,

Michael.

-- 
Michael Opdenacker, Free Electrons
Free Embedded Linux Training Materials
on http://free-electrons.com/training
(More than 1500 pages!)


  reply	other threads:[~2008-02-09  9:29 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 22:47 [PATCH] x86 (Linux Tiny): configure out support for some processors Michael Opdenacker
2008-02-08 23:04 ` H. Peter Anvin
2008-02-08 23:11 ` Ingo Molnar
2008-02-09  9:31   ` Michael Opdenacker
2008-02-11 22:42   ` Michael Opdenacker
2008-02-11 22:56     ` Matt Mackall
2008-02-11 23:01       ` H. Peter Anvin
2008-02-11 23:28         ` Matt Mackall
2008-02-12  0:54           ` H. Peter Anvin
2008-02-12  1:15             ` Matt Mackall
2008-02-15 11:00             ` [RFC] [PATCH] x86: Use ELF section to list CPU vendor specific code (Linux Tiny) Thomas Petazzoni
2008-02-17 18:14               ` Ingo Molnar
2008-02-17 19:46                 ` H. Peter Anvin
2008-02-23  2:43               ` Matt Mackall
2008-02-23  3:19                 ` H. Peter Anvin
2008-02-25  8:29                 ` Thomas Petazzoni
2008-02-25 17:03                   ` Matt Mackall
2008-02-25 17:53                     ` Thomas Petazzoni
2008-02-25 17:58                       ` Matt Mackall
2008-02-11 22:59     ` [PATCH] x86 (Linux Tiny): configure out support for some processors H. Peter Anvin
2008-02-08 23:20 ` Matt Mackall
2008-02-09  8:30   ` Simon Holm Thøgersen
2008-02-09  9:29     ` Michael Opdenacker [this message]
2008-02-09 10:05       ` Simon Holm Thøgersen
2008-02-09 21:35       ` H. Peter Anvin
2008-02-09  9:26   ` Michael Opdenacker
2008-02-09  3:48 ` Taral

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=47AD725E.6050903@free-electrons.com \
    --to=michael-lists@free-electrons.com \
    --cc=Linux-tiny@selenic.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mpm@selenic.com \
    --cc=odie@cs.aau.dk \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.