From: Peter Zijlstra Subject: Re: randconfig build error with next-20150529, in crypto/jitterentropy.c Date: Mon, 08 Jun 2015 14:36:30 +0200 Message-ID: <1433766990.1495.39.camel@twins> References: <20150608122502.GA29454@gondor.apana.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Cc: Andy Shevchenko , Jim Davis , Stephen Rothwell , linux-next , linux-kernel , "David S. Miller" , linux-crypto , Waiman Long , Ingo Molnar , "x86@kernel.org" , smueller@chronox.de To: Herbert Xu Return-path: In-Reply-To: <20150608122502.GA29454@gondor.apana.org.au> Sender: linux-next-owner@vger.kernel.org List-Id: linux-crypto.vger.kernel.org Adding Stephan to Cc. On Mon, 2015-06-08 at 20:25 +0800, Herbert Xu wrote: > On Mon, Jun 08, 2015 at 03:21:09PM +0300, Andy Shevchenko wrote: > > On Fri, May 29, 2015 at 10:14 PM, Jim Davis wrote: > > > Building with the attached random configuration file, > > > > Hit the very same error against next-20150605. > > > > The issue with that file we have no compiler optimization enabled. So, > > guys, how you would recommend to fix it? > > Stephan, can we get rid of the no optimisation requirement? Would something like #pragma GCC push_options #pragma GCC optimize ("-O0") static __u64 jent_fold_time(struct rand_data *ec, __u64 time, __u64 *folded, __u64 loop_cnt) { ... } #pragma GCC pop_options Be an option to allow the file to be compiled with regular optimizations enabled?