linux-kernel - sched.c: why -fno-omit-frame-pointer?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 19 Aug 2007 16:17:32 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	linux-kernel@...r.kernel.org, Andreas Schwab <schwab@...e.de>,
	Alan Modra <alan@...uxcare.com.au>,
	David Mosberger-Tang <davidm@....hp.com>
Subject: sched.c: why -fno-omit-frame-pointer?

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/