linux-kernel - Re: 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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 19 Aug 2007 14:05:23 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Adrian Bunk <bunk@...nel.org>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Andreas Schwab <schwab@...e.de>,
	Alan Modra <alan@...uxcare.com.au>,
	David Mosberger-Tang <davidm@....hp.com>
Subject: Re: sched.c: why -fno-omit-frame-pointer?


On Sun, 2007-08-19 at 16:17 +0200, Adrian Bunk wrote:
> 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.
> 

vague memory: this was needed for wchan to work properly


-
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/