linux-kernel - Re: [PATCH] x86: unify x86 Makefile(s)

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: <20071228221324.GA9105@does.not.exist>
Date:	Sat, 29 Dec 2007 00:13:24 +0200
From:	Adrian Bunk <bunk@...nel.org>
To:	Sam Ravnborg <sam@...nborg.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...e.de>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: unify x86 Makefile(s)

On Fri, Dec 28, 2007 at 10:23:41PM +0100, Sam Ravnborg wrote:
>...
> Noteworthy remarks on the unification:
>...
> - -funit-at-a-time should be easy to unify but it looks like we have a bug
>   in 32 bit. We only enable -funit-at-a-time for gcc less than 0400 if they
>   support it

No, we _dis_able it on 32bit if a gcc < 4.0 supports it.

> (and I recall it is a gcc 4.00 feature). [-lt -> -gt]
>...

unit-at-a-time was introduced in upstream gcc 3.4 and backported to some 
popular 3.3 x86_64 branch.

i386 and x86_64 go in exactly opposite directions regarding when to use 
unit-at-a-time, but that was intentional and we should keep it that way.

> 	Sam
>...


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/