public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Stephan Mueller <smueller@chronox•de>
To: Guenter Roeck <linux@roeck-us•net>
Cc: 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>,
	Herbert Xu <herbert@gondor•apana.org.au>,
	"David S. Miller" <davem@davemloft•net>,
	linux-crypto <linux-crypto@vger•kernel.org>
Subject: Re: randconfig build error with next-20150529, in crypto/jitterentropy.c
Date: Tue, 09 Jun 2015 01:33:12 +0200	[thread overview]
Message-ID: <1702795.h60qkgijGA@tauon.atsec.com> (raw)
In-Reply-To: <55762581.6070809@roeck-us.net>

Am Monday 08 June 2015, 16:30:09 schrieb Guenter Roeck:

Hi Guenter,

>
>get_cycles is implemented as static inline which executes mfspr(SPR_TTCR).
>SPR_TTCR is a constant. Normally that information seems to be passed on,
>but not when get_cycles() is compiled through jitterentropy.
>
>Any idea what might cause this ?

Then it may be the optimization issue as well that Peter indicated. May I ask 
you for testing purposes (I do not have an OpenRISC) to remove the following 
line from crypto/Makefile:

CFLAGS_jitterentropy.o = -O0

Note, that should just serve for testing. I will post a patch later that will 
replace the -O0 statement with a pragma.

Thanks a lot.
>
>Thanks,
>Guenter


Ciao
Stephan

next prev parent reply	other threads:[~2015-06-08 23:33 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
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 [this message]
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=1702795.h60qkgijGA@tauon.atsec.com \
    --to=smueller@chronox$(echo .)de \
    --cc=andy.shevchenko@gmail$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=jim.epost@gmail$(echo .)com \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=linux@roeck-us$(echo .)net \
    --cc=sfr@canb$(echo .)auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox