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]

Message-ID: <20060906235029.GC25473@stusta.de>
Date:	Thu, 7 Sep 2006 01:50:29 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Roman Zippel <zippel@...ux-m68k.org>
Cc:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...l.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [2.6 patch] re-add -ffreestanding

On Thu, Sep 07, 2006 at 01:38:01AM +0200, Roman Zippel wrote:
> Hi,

Hi Roman,

> On Thu, 7 Sep 2006, Adrian Bunk wrote:
> 
> > We are talking about reverting the patch that removed -ffreestanding, 
> > and that broke at least two architectures although it wrongly claimed 
> > it would have been a safe patch.
> 
> Your patch is nevertheless the wrong fix for one of these archs.

it's correct, since with -ffreestanding gcc no longer has the right to 
assume it had a full libc available.

Yes, -ffreestanding disables gcc builtins, but the correct fix for this 
issue is not to remove -ffreestanding, but to check where we want to use 
gcc builtins and enable them explicitely.

This takes more time than the quick'n'dirty patch that removed 
-ffreestanding, but it does it right (and we might perhaps get rid of 
things like include/asm-i386/string.h).

> bye, Roman

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/