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: <20180320124445.3bb1da1c@lwn.net>
Date:   Tue, 20 Mar 2018 12:44:45 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     mingo@...nel.org, tglx@...utronix.de, linux-kernel@...r.kernel.org,
        torvalds@...ux-foundation.org
Subject: Re: [PATCH 1/2] x86: Force asm-goto

On Tue, 20 Mar 2018 16:50:36 +0100
Peter Zijlstra <peterz@...radead.org> wrote:

> > Given that, how about a patch to Documentation/Changes to reflect the new
> > reality?  It's not in RST yet, so you should be able to go there without
> > ill effect :)  
> 
> 
> That thing says:
> 
>   GCC
>   ---
> 
>   The gcc version requirements may vary depending on the type of CPU in your
>   computer. jon
> 
> Which is still entirely accurate. And afaik the 3.2 minimum listed there
> still works for !x86.

Well, other recent discussions established that nothing earlier than 4.1
has been observed to work anywhere for some time.

I guess what we really need is a little table of architecture-specific
minimum GCC versions so that our users actually know what's required.
I'll see if I can find a moment to pull that together at some point.

jon

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ