Change the default purgatory sha256 code optimization from -O0 to -O2, and add a
new arch specific makefile variable $(ARCH)_PURGATORY_SHA256_CFLAGS which can
over ride this default. Set ia64_PURGATORY_SHA256_CFLAGS to -O0 to retain the
previous optimization level for ia64.
The purgatory sha256 c
Change the default purgatory sha256 code optimization from -O0 to -O2, and add a
new arch specific makefile variable $(ARCH)_PURGATORY_SHA256_CFLAGS which can
over ride this default. Set ia64_PURGATORY_SHA256_CFLAGS to -O0 to retain the
previous optimization level for ia64.
The purgatory sha256
On Wed, Nov 23, 2016 at 09:57:09AM -0800, Geoff Levand wrote:
> Change the default purgatory sha256 code optimization from -O0 to -O2, and
> add a
> new arch specific makefile variable $(ARCH)_PURGATORY_SHA256_CFLAGS which can
> over ride this default. Set ia64_PURGATORY_SHA256_CFLAGS to -O0 to r
On Thu, Nov 24, 2016 at 1:23 PM, Simon Horman wrote:
> On Wed, Nov 23, 2016 at 09:57:09AM -0800, Geoff Levand wrote:
>> Change the default purgatory sha256 code optimization from -O0 to -O2, and
>> add a
>> new arch specific makefile variable $(ARCH)_PURGATORY_SHA256_CFLAGS which can
>> over ride
On Mon, Nov 28, 2016 at 11:14:38AM +0530, Pratyush Anand wrote:
> On Thu, Nov 24, 2016 at 1:23 PM, Simon Horman wrote:
> > On Wed, Nov 23, 2016 at 09:57:09AM -0800, Geoff Levand wrote:
> >> Change the default purgatory sha256 code optimization from -O0 to -O2, and
> >> add a
> >> new arch specifi
Hi Simon,
On 11/30/2016 03:02 AM, Simon Horman wrote:
> This patch doesn't seem to apply against the master branch.
> I'm wondering if you or Geoff could:
>
> 1. Rebase the patch
> 2. Include some text about the performance improvement.
>Something like what is above would be fine from my pov.