From: Stephan Mueller <smueller@chronox.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Jim Davis <jim.epost@gmail.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next <linux-next@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
linux-crypto <linux-crypto@vger.kernel.org>,
Waiman Long <Waiman.Long@hp.com>, Ingo Molnar <mingo@kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
fengguang.wu@intel.com
Subject: Re: randconfig build error with next-20150529, in crypto/jitterentropy.c
Date: Mon, 08 Jun 2015 14:44:47 +0200 [thread overview]
Message-ID: <179222904.HonSY4bzy7@tachyon.chronox.de> (raw)
In-Reply-To: <1433766990.1495.39.camel@twins>
Am Montag, 8. Juni 2015, 14:36:30 schrieb Peter Zijlstra:
Hi Peter,
> 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 <jim.epost@gmail.com> 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?
Yes, that is also possible. I was not aware of the fact that the optimization
is the problem. I got another report fom Fengguang Wu about a compile issue on
AVR32 which I found out relates to the same issue.
I will prepare a patch shortly.
--
Ciao
Stephan
next prev parent reply other threads:[~2015-06-08 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 19:14 randconfig build error with next-20150529, in crypto/jitterentropy.c Jim Davis
2015-06-08 12:21 ` Andy Shevchenko
2015-06-08 12:25 ` Herbert Xu
2015-06-08 12:36 ` Peter Zijlstra
2015-06-08 12:44 ` Stephan Mueller [this message]
2015-06-08 15:52 ` Stephan Mueller
2015-06-08 15:59 ` Peter Zijlstra
2015-06-08 19:54 ` Guenter Roeck
2015-06-08 22:36 ` Stephan Mueller
2015-06-08 23:30 ` Guenter Roeck
2015-06-08 23:33 ` Stephan Mueller
2015-06-08 23:51 ` Guenter Roeck
2015-06-09 0:10 ` Stephan Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179222904.HonSY4bzy7@tachyon.chronox.de \
--to=smueller@chronox.de \
--cc=Waiman.Long@hp.com \
--cc=andy.shevchenko@gmail.com \
--cc=davem@davemloft.net \
--cc=fengguang.wu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=jim.epost@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).