| 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
| ||
|
Message-ID: <50339A85.3080206@redhat.com> Date: Tue, 21 Aug 2012 17:26:13 +0300 From: Avi Kivity <avi@...hat.com> To: Ingo Molnar <mingo@...nel.org> CC: Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org, x86@...nel.org, mmarek@...e.cz, linux-kbuild@...r.kernel.org, JBeulich@...e.com, akpm@...ux-foundation.org, Linus Torvalds <torvalds@...ux-foundation.org>, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: RFC: Link Time Optimization support for the kernel On 08/21/2012 10:49 AM, Ingo Molnar wrote: > > Can the current implementation of LTO optimize to the level of > inlining? A lot of our include file hell situation results from > the desire to declare structures publicly so that inlined > functions can use them directly. > > If data structures could be encapsulated/internalized to > subsystems and only global functions are exposed to other > subsystems [which are then LTO optimized] then our include > file dependencies could become a *lot* simpler. I think modules break this (if I understand what you mean correctly). If the main kernel exposes symbol x as a global function, then lto will not inline it into a module. -- error compiling committee.c: too many arguments to function -- 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/
Powered by blists - more mailing lists