linux-kernel - Re: [2.6 patch] re-add -ffreestanding

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 for Android: free password hash cracker in your pocket

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

Date:	Thu, 7 Sep 2006 03:23:31 +0200 (CEST)
From:	Roman Zippel <zippel@...ux-m68k.org>
To:	Adrian Bunk <bunk@...sta.de>
cc:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] re-add -ffreestanding

Hi,

On Thu, 7 Sep 2006, Adrian Bunk wrote:

> > Define "full libc".
> 
> Everything described in clause 7 of ISO/IEC 9899:1999.

Its behaviour is also defined by the environment, so what gcc can assume 
is rather limited and you have not shown a single example, that any such 
assumption would be invalid for the kernel.

> > Explain what exactly -ffreestanding fixes, which is not valid for the 
> > kernel.
> 
> It's simply correct since the kernel doesn't provide everything 
> described in clause 7 of ISO/IEC 9899:1999.
> 
> And it fixes compile errors caused by the fact that gcc is otherwise 
> allowed to replace calls to any standard C function with semantically 
> equivalent calls to other standard C functions - in a hosted environment 
> the latter are guaranteed to be present.

The kernel uses standard C, so your point is?
You already got two NACKs from arch maintainers, why the hell are you 
still pushing this patch? The builtin functions are useful and you want to 
force arch maintainers to have to enable every single one manually and 
to maintain a list of these functions over multiple versions of gcc?

bye, Roman
-
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/