linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karthik Bhargavan <karthikeyan.bhargavan@inria.fr>
To: "Jason A. Donenfeld" <jason@zx2c4.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: x86/curve25519 - Remove unused carry variables
Date: Mon, 27 Jul 2020 17:10:09 +0200	[thread overview]
Message-ID: <D851245D-A712-40C4-BC8F-D677C0252ABA@inria.fr> (raw)
In-Reply-To: <4DE9D3CD-E934-49CE-A122-F536721ADF72@inria.fr>

Reviewed-by: Karthikeyan Bhargavan <karthik.bhargavan@gmail.com>

> On 27 Jul 2020, at 17:08, Karthik Bhargavan <karthikeyan.bhargavan@inria.fr> wrote:
> 
> Removing unused variables is harmless. (GCC would do this automaticelly.)
> So this change seems fine.
> 
> -Karthik
> 
>> On 23 Jul 2020, at 12:05, Jason A. Donenfeld <jason@zx2c4.com> wrote:
>> 
>> Hi Herbert,
>> 
>> On Thu, Jul 23, 2020 at 9:51 AM Herbert Xu <herbert@gondor.apana.org.au> wrote:
>>> 
>>> The carry variables are assigned but never used, which upsets
>>> the compiler.  This patch removes them.
>>> 
>>> Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
>>> 
>>> diff --git a/arch/x86/crypto/curve25519-x86_64.c b/arch/x86/crypto/curve25519-x86_64.c
>>> index 8a17621f7d3a..8acbb6584a37 100644
>>> --- a/arch/x86/crypto/curve25519-x86_64.c
>>> +++ b/arch/x86/crypto/curve25519-x86_64.c
>>> @@ -948,10 +948,8 @@ static void store_felem(u64 *b, u64 *f)
>>> {
>>>       u64 f30 = f[3U];
>>>       u64 top_bit0 = f30 >> (u32)63U;
>>> -       u64 carry0;
>>>       u64 f31;
>>>       u64 top_bit;
>>> -       u64 carry;
>>>       u64 f0;
>>>       u64 f1;
>>>       u64 f2;
>>> @@ -970,11 +968,11 @@ static void store_felem(u64 *b, u64 *f)
>>>       u64 o2;
>>>       u64 o3;
>>>       f[3U] = f30 & (u64)0x7fffffffffffffffU;
>>> -       carry0 = add_scalar(f, f, (u64)19U * top_bit0);
>>> +       add_scalar(f, f, (u64)19U * top_bit0);
>>>       f31 = f[3U];
>>>       top_bit = f31 >> (u32)63U;
>>>       f[3U] = f31 & (u64)0x7fffffffffffffffU;
>>> -       carry = add_scalar(f, f, (u64)19U * top_bit);
>>> +       add_scalar(f, f, (u64)19U * top_bit);
>>>       f0 = f[0U];
>>>       f1 = f[1U];
>>>       f2 = f[2U];
>>> --
>> 
>> That seems obvious and reasonable, and so I'm inclined to ack this,
>> but I first wanted to give Karthik (CC'd) a chance to chime in here,
>> as it's his HACL* project that's responsible, and he might have some
>> curious insight.
>> 
>> Jason
> 


  reply	other threads:[~2020-07-27 15:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  7:50 [PATCH] crypto: x86/curve25519 - Remove unused carry variables Herbert Xu
2020-07-23 10:05 ` Jason A. Donenfeld
2020-07-27 15:08   ` Karthik Bhargavan
2020-07-27 15:10     ` Karthik Bhargavan [this message]
2020-07-27 15:10     ` Jason A. Donenfeld

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=D851245D-A712-40C4-BC8F-D677C0252ABA@inria.fr \
    --to=karthikeyan.bhargavan@inria.fr \
    --cc=herbert@gondor.apana.org.au \
    --cc=jason@zx2c4.com \
    --cc=linux-crypto@vger.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).