From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [PATCH 0/3] Add __ioread32_copy() and use it Date: Sat, 19 Sep 2015 22:16:29 +0200 Message-ID: <20150919201628.GI1747@two.firstfloor.org> References: <1442346089-32077-1-git-send-email-sboyd@codeaurora.org> <20150915155815.5a41a8dc537610ab44d8d3dc@linux-foundation.org> <20150916023219.GD1747@two.firstfloor.org> <20150915195031.0a1756a2.akpm@linux-foundation.org> <20150916025546.GE1747@two.firstfloor.org> <20150918121919.fa20552946703ae772d636e9@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20150918121919.fa20552946703ae772d636e9@linux-foundation.org> Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-subscribe: List-owner: List-post: List-archive: To: Andrew Morton Cc: Andi Kleen , Stephen Boyd , Andy Gross , linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-soc@vger.kernel.org, linux-mips@linux-mips.org, Hauke Mehrtens , Paul Walmsley , =?utf-8?B?UmFmYcWCIE1pxYJlY2tp?= , Bjorn Andersson List-Id: linux-arm-msm@vger.kernel.org On Fri, Sep 18, 2015 at 12:19:19PM -0700, Andrew Morton wrote: > On Wed, 16 Sep 2015 04:55:46 +0200 Andi Kleen wrote: > > > > Under what circumstances will the compiler (or linker?) do this? > > > > Compiler. > > > > > LTO enabled? > > > > Yes it's for LTO. The optimization allows the compiler to drop unused > > functions, which is very popular with users (a lot use it to get smaller > > kernel images) > > > > Does this look truthful and complete? > > > --- a/include/linux/compiler-gcc.h~a > +++ a/include/linux/compiler-gcc.h > @@ -205,7 +205,10 @@ > > #if GCC_VERSION >= 40600 > /* > - * Tell the optimizer that something else uses this function or variable. > + * When used with Link Time Optimization, gcc can optimize away C functions or > + * variables which are referenced only from assembly code. __visible tells the > + * optimizer that something else uses this function or variable, thus preventing > + * this. Yes, In a few cases I also used it to work around LTO bugs in older gcc releases. I don't think any of those fixes made it into mainline though, and they are not needed anymore with 5.x -Andi