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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 22 Aug 2006 12:37:13 +0200
From:	Andi Kleen <ak@...e.de>
To:	Kyle Moffett <mrmacman_g4@....com>
Cc:	Adrian Bunk <bunk@...sta.de>, linux-kernel@...r.kernel.org,
	Roman Zippel <zippel@...ux-m68k.org>
Subject: Re: [2.6 patch] re-add -ffreestanding

On Mon, 21 Aug 2006 23:37:31 -0400
Kyle Moffett <mrmacman_g4@....com> wrote:

> On Aug 21, 2006, at 19:13:20, Andi Kleen wrote:
> >> What's the problem with adding -ffreestanding and stating  
> >> explicitely which functions we want to be handled be builtins, and  
> >> which functions we don't want to be handled by builtins?
> >
> > Take a look at lib/string.c and think about it a bit.
> 
> So why can't lib/string.c explicitly say __builtin_foo() instead of  
> foo() where we mean the former? 

Because gcc when using builtins sometimes decides to call the 
out of line version (usually when it can't figure out the alignment
and generic alignment code would be too large to inline). And it will
always call str/memfoo not __builtin_str/memfoo

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