linux-kernel - Re: [PATCH] lto: Add __noreorder and mark initcalls _

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: <20150410143629.aaba355c08d3b71e5c1cddd0@linux-foundation.org>
Date:	Fri, 10 Apr 2015 14:36:29 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	mmarek@...e.cz, linux-kbuild@...r.kernel.org,
	linux-kernel@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
	hubicka@....cz
Subject: Re: [PATCH] lto: Add __noreorder and mark initcalls __noreorder

On Thu, 9 Apr 2015 01:50:23 +0200 Andi Kleen <andi@...stfloor.org> wrote:

> > Head is spinning a bit.  As this all appears to be shiny new
> > added-by-andi gcc functionality, it would be useful if we could have a
> > few more words describing what it's all about.  Reordering of what with
> > respect to what and why and why is it bad.  Why is gcc reordering
> > things anyway, and what's the downside of preventing this.  Why is the
> > compiler reordering things rather than the linker. etc etc etc.
> 
> Ok, let me try.

That was super-useful, thanks.  I slurped it into the changelog -
maybe one day it will provide material for Documentation/lto-stuff.txt.

Big picture: do you have a feeling for how much benefit LTO will yield
in the kernel, if/when it's all completed?

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