MirOS Manual: BN_add_word(3), BN_div_word(3), BN_mod_word(3), BN_mul_word(3), BN_sub_word(3)


BN_ADD_WORD(3)               OpenSSL               BN_ADD_WORD(3)

NAME

     BN_add_word, BN_sub_word, BN_mul_word, BN_div_word,
     BN_mod_word - arithmetic functions on BIGNUMs with integers

SYNOPSIS

      #include <openssl/bn.h>

      int BN_add_word(BIGNUM *a, BN_ULONG w);

      int BN_sub_word(BIGNUM *a, BN_ULONG w);

      int BN_mul_word(BIGNUM *a, BN_ULONG w);

      BN_ULONG BN_div_word(BIGNUM *a, BN_ULONG w);

      BN_ULONG BN_mod_word(const BIGNUM *a, BN_ULONG w);

DESCRIPTION

     These functions perform arithmetic operations on BIGNUMs
     with unsigned integers. They are much more efficient than
     the normal BIGNUM arithmetic operations.

     BN_add_word() adds w to a ("a+=w").

     BN_sub_word() subtracts w from a ("a-=w").

     BN_mul_word() multiplies a and w ("a*=b").

     BN_div_word() divides a by w ("a/=w") and returns the
     remainder.

     BN_mod_word() returns the remainder of a divided by w
     ("a%m").

     For BN_div_word() and BN_mod_word(), w must not be 0.

RETURN VALUES

     BN_add_word(), BN_sub_word() and BN_mul_word() return 1 for
     success, 0 on error. The error codes can be obtained by
     ERR_get_error(3).

     BN_mod_word() and BN_div_word() return a%w.

SEE ALSO

     bn(3), ERR_get_error(3), BN_add(3)

HISTORY

     BN_add_word() and BN_mod_word() are available in all ver-
     sions of SSLeay and OpenSSL. BN_div_word() was added in
     SSLeay 0.8, and BN_sub_word() and BN_mul_word() in SSLeay
     0.9.0.

MirOS BSD #10-current      2005-02-05                           1

Generated on 2017-04-03 16:26:17 by $MirOS: src/scripts/roff2htm,v 1.88 2017/01/29 00:51:06 tg Exp $

These manual pages and other documentation are copyrighted by their respective writers; their source is available at our CVSweb, AnonCVS, and other mirrors. The rest is Copyright © 2002–2017 The MirOS Project, Germany.
This product includes material provided by mirabilos.

This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report — diffs preferred.