From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Stephan Mueller <smueller@chronox•de>
Cc: herbert@gondor•apana.org.au,
Peter Zijlstra
<public-peterz-wegcikhe2lqwvfeawa7xhq@plane•gmane.org>,
Andy Shevchenko <andy.shevchenko@gmail•com>,
Jim Davis <jim.epost@gmail•com>,
Linux-Next <linux-next@vger•kernel.org>,
linux-kernel@vger•kernel.org,
"David S. Miller" <davem@davemloft•net>,
linux-crypto@vger•kernel.org, Waiman Long <waiman.long@hp•com>,
Ingo Molnar <mingo@kernel•org>, x86 <x86@kernel•org>,
Guenter Roeck <linux@roeck-us•net>
Subject: Re: [PATCH] crypto: drbg - use pragmas for disabling optimization
Date: Tue, 9 Jun 2015 13:22:58 +1000 [thread overview]
Message-ID: <20150609132258.26f6b108@canb.auug.org.au> (raw)
In-Reply-To: <3181127.KGS6GDHCq6@tachyon.chronox.de>
[-- Attachment #1: Type: text/plain, Size: 613 bytes --]
Hi Stephan,
On Tue, 09 Jun 2015 04:08:49 +0200 Stephan Mueller <smueller@chronox•de> wrote:
>
> Replace the global -O0 compiler flag from the Makefile with GCC
> pragmas to mark only the functions required to be compiled without
> optimizations.
>
> This patch also adds a comment describing the rationale for the
> functions chosen to be compiled without optimizations.
>
> Signed-off-by: Stephan Mueller <smueller@chronox•de>
I will add this as a fix patch to the crypto tree merge today (unless
someone yells at me).
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-09 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 2:08 [PATCH] crypto: drbg - use pragmas for disabling optimization Stephan Mueller
2015-06-09 3:22 ` Stephen Rothwell [this message]
2015-06-09 4:31 ` Guenter Roeck
2015-06-09 4:46 ` nios2: Export get_cycles Herbert Xu
2015-06-09 5:19 ` Stephen Rothwell
2015-06-09 5:50 ` Herbert Xu
2015-06-09 14:35 ` [PATCH] crypto: drbg - use pragmas for disabling optimization Herbert Xu
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=20150609132258.26f6b108@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--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=mingo@kernel$(echo .)org \
--cc=public-peterz-wegcikhe2lqwvfeawa7xhq@plane$(echo .)gmane.org \
--cc=smueller@chronox$(echo .)de \
--cc=waiman.long@hp$(echo .)com \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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