public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andreas Schwab <schwab@suse.de>,
	Alan Modra <alan@linuxcare.com.au>,
	David Mosberger-Tang <davidm@hpl.hp.com>
Subject: sched.c: why -fno-omit-frame-pointer?
Date: Sun, 19 Aug 2007 16:17:32 +0200	[thread overview]
Message-ID: <20070819141732.GD32595@stusta.de> (raw)

kernel/sched.c gets compiled with -fno-omit-frame-pointer, and this was 
already done in kernel 1.0 (sic).

Later, it has been modified to be this way only on some architectures.

It might not be an earthshaking amount, but removing it saves some 
bytes, and there's no visible breakage when running the modified kernel 
on i386.

$ ls -la kernel/sched.o*
-rw-rw-r-- 1 bunk bunk 25600 2007-08-19 16:10 kernel/sched.o
-rw-rw-r-- 1 bunk bunk 26084 2007-08-19 16:03 kernel/sched.o.old
$ size kernel/sched.o*
   text    data     bss     dec     hex filename
  11835     184    2000   14019    36c3 kernel/sched.o
  12321     184    2000   14505    38a9 kernel/sched.o.old
$ 

Is the -fno-omit-frame-pointer still required for some reason, or is 
this a relict that could be removed?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


             reply	other threads:[~2007-08-19 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-19 14:17 Adrian Bunk [this message]
2007-08-19 21:05 ` sched.c: why -fno-omit-frame-pointer? Arjan van de Ven
2007-08-19 23:00 ` Andi Kleen
2007-08-23 11:30   ` Ingo Molnar

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=20070819141732.GD32595@stusta.de \
    --to=bunk@kernel.org \
    --cc=alan@linuxcare.com.au \
    --cc=davidm@hpl.hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=schwab@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox