curve25519-dalek-source/src/backend/vector/scalar_mul/mod.rs

// -*- mode: rust; -*-
//
// This file is part of curve25519-dalek.
// Copyright (c) 2016-2021 isis lovecruft
// Copyright (c) 2016-2019 Henry de Valence
// See LICENSE for licensing information.
//
// Authors:
// - isis agora lovecruft <isis@patternsinthevoid.net>
// - Henry de Valence <hdevalence@hdevalence.ca>

pub mod variable_base;

pub mod vartime_double_base;

#[cfg(feature = "alloc")]
pub mod straus;

#[cfg(feature = "alloc")]
pub mod precomputed_straus;

#[cfg(feature = "alloc")]
pub mod pippenger;
Split out constant-time variable-base scalar mul. The serial (`u32`/`u64`) implementations use a multiple curve models, passing between extended and projective coordinates when performing addition and doubling (respectively). But the AVX2 backend doesn't, so in order to write a single scalar mult implementation, we have to either abstract over the curve models or have two implementations. A generic solution is possible but extremely unreadable: the scalar mul implementation would be parameterized over the point types used by the serial implementations, with many where clauses describing how the types relate. The AVX2 types could then be substituted in the appropriate places. Instead we just duplicate the code into the `avx2` backend. 2018-03-26 22:01:48 +00:00			`// -- mode: rust; --`
			`//`
			`// This file is part of curve25519-dalek.`
Update copyright years. 2021-08-03 23:13:45 +00:00			`// Copyright (c) 2016-2021 isis lovecruft`
			`// Copyright (c) 2016-2019 Henry de Valence`
Split out constant-time variable-base scalar mul. The serial (`u32`/`u64`) implementations use a multiple curve models, passing between extended and projective coordinates when performing addition and doubling (respectively). But the AVX2 backend doesn't, so in order to write a single scalar mult implementation, we have to either abstract over the curve models or have two implementations. A generic solution is possible but extremely unreadable: the scalar mul implementation would be parameterized over the point types used by the serial implementations, with many where clauses describing how the types relate. The AVX2 types could then be substituted in the appropriate places. Instead we just duplicate the code into the `avx2` backend. 2018-03-26 22:01:48 +00:00			`// See LICENSE for licensing information.`
			`//`
			`// Authors:`
Update copyright years. 2021-08-03 23:13:45 +00:00			`// - isis agora lovecruft <isis@patternsinthevoid.net>`
Split out constant-time variable-base scalar mul. The serial (`u32`/`u64`) implementations use a multiple curve models, passing between extended and projective coordinates when performing addition and doubling (respectively). But the AVX2 backend doesn't, so in order to write a single scalar mult implementation, we have to either abstract over the curve models or have two implementations. A generic solution is possible but extremely unreadable: the scalar mul implementation would be parameterized over the point types used by the serial implementations, with many where clauses describing how the types relate. The AVX2 types could then be substituted in the appropriate places. Instead we just duplicate the code into the `avx2` backend. 2018-03-26 22:01:48 +00:00			`// - Henry de Valence <hdevalence@hdevalence.ca>`

			`pub mod variable_base;`
Pull out constant-time straus implementation 2018-03-26 22:32:20 +00:00
Pull out vartime double-base scalar mul code 2018-03-27 00:02:59 +00:00			`pub mod vartime_double_base;`

Add vector implementation of precomputation. 2019-02-12 19:36:34 +00:00			`#[cfg(feature = "alloc")]`
Pull out constant-time straus implementation 2018-03-26 22:32:20 +00:00			`pub mod straus;`
Add vector implementation of precomputation. 2019-02-12 19:36:34 +00:00
			`#[cfg(feature = "alloc")]`
			`pub mod precomputed_straus;`
cgs 2019-05-21 20:31:50 +00:00
			`#[cfg(feature = "alloc")]`
			`pub mod pippenger;`