os/ossrv/ssl/libcrypto/src/crypto/md5/md5_locl.h
author sl
Tue, 10 Jun 2014 14:32:02 +0200
changeset 1 260cb5ec6c19
permissions -rw-r--r--
Update contrib.
sl@0
     1
/* crypto/md5/md5_locl.h */
sl@0
     2
/* Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com)
sl@0
     3
 * All rights reserved.
sl@0
     4
 *
sl@0
     5
 * This package is an SSL implementation written
sl@0
     6
 * by Eric Young (eay@cryptsoft.com).
sl@0
     7
 * The implementation was written so as to conform with Netscapes SSL.
sl@0
     8
 * 
sl@0
     9
 * This library is free for commercial and non-commercial use as long as
sl@0
    10
 * the following conditions are aheared to.  The following conditions
sl@0
    11
 * apply to all code found in this distribution, be it the RC4, RSA,
sl@0
    12
 * lhash, DES, etc., code; not just the SSL code.  The SSL documentation
sl@0
    13
 * included with this distribution is covered by the same copyright terms
sl@0
    14
 * except that the holder is Tim Hudson (tjh@cryptsoft.com).
sl@0
    15
 * 
sl@0
    16
 * Copyright remains Eric Young's, and as such any Copyright notices in
sl@0
    17
 * the code are not to be removed.
sl@0
    18
 * If this package is used in a product, Eric Young should be given attribution
sl@0
    19
 * as the author of the parts of the library used.
sl@0
    20
 * This can be in the form of a textual message at program startup or
sl@0
    21
 * in documentation (online or textual) provided with the package.
sl@0
    22
 * 
sl@0
    23
 * Redistribution and use in source and binary forms, with or without
sl@0
    24
 * modification, are permitted provided that the following conditions
sl@0
    25
 * are met:
sl@0
    26
 * 1. Redistributions of source code must retain the copyright
sl@0
    27
 *    notice, this list of conditions and the following disclaimer.
sl@0
    28
 * 2. Redistributions in binary form must reproduce the above copyright
sl@0
    29
 *    notice, this list of conditions and the following disclaimer in the
sl@0
    30
 *    documentation and/or other materials provided with the distribution.
sl@0
    31
 * 3. All advertising materials mentioning features or use of this software
sl@0
    32
 *    must display the following acknowledgement:
sl@0
    33
 *    "This product includes cryptographic software written by
sl@0
    34
 *     Eric Young (eay@cryptsoft.com)"
sl@0
    35
 *    The word 'cryptographic' can be left out if the rouines from the library
sl@0
    36
 *    being used are not cryptographic related :-).
sl@0
    37
 * 4. If you include any Windows specific code (or a derivative thereof) from 
sl@0
    38
 *    the apps directory (application code) you must include an acknowledgement:
sl@0
    39
 *    "This product includes software written by Tim Hudson (tjh@cryptsoft.com)"
sl@0
    40
 * 
sl@0
    41
 * THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND
sl@0
    42
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
sl@0
    43
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
sl@0
    44
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
sl@0
    45
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
sl@0
    46
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
sl@0
    47
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
sl@0
    48
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
sl@0
    49
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
sl@0
    50
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
sl@0
    51
 * SUCH DAMAGE.
sl@0
    52
 * 
sl@0
    53
 * The licence and distribution terms for any publically available version or
sl@0
    54
 * derivative of this code cannot be changed.  i.e. this code cannot simply be
sl@0
    55
 * copied and put under another distribution licence
sl@0
    56
 * [including the GNU Public Licence.]
sl@0
    57
 */
sl@0
    58
sl@0
    59
#include <stdlib.h>
sl@0
    60
#include <string.h>
sl@0
    61
#include <openssl/e_os2.h>
sl@0
    62
#include <openssl/md5.h>
sl@0
    63
sl@0
    64
#ifndef MD5_LONG_LOG2
sl@0
    65
#define MD5_LONG_LOG2 2 /* default to 32 bits */
sl@0
    66
#endif
sl@0
    67
sl@0
    68
#ifdef MD5_ASM
sl@0
    69
# if defined(__i386) || defined(__i386__) || defined(_M_IX86) || defined(__INTEL__) || defined(__x86_64) || defined(__x86_64__)
sl@0
    70
#  if !defined(B_ENDIAN)
sl@0
    71
#   define md5_block_host_order md5_block_asm_host_order
sl@0
    72
#  endif
sl@0
    73
# elif defined(__sparc) && defined(OPENSSL_SYS_ULTRASPARC)
sl@0
    74
   void md5_block_asm_data_order_aligned (MD5_CTX *c, const MD5_LONG *p,size_t num);
sl@0
    75
#  define HASH_BLOCK_DATA_ORDER_ALIGNED md5_block_asm_data_order_aligned
sl@0
    76
# endif
sl@0
    77
#endif
sl@0
    78
sl@0
    79
void md5_block_host_order (MD5_CTX *c, const void *p,size_t num);
sl@0
    80
void md5_block_data_order (MD5_CTX *c, const void *p,size_t num);
sl@0
    81
sl@0
    82
#if defined(__i386) || defined(__i386__) || defined(_M_IX86) || defined(__INTEL__) || defined(__x86_64) || defined(__x86_64__)
sl@0
    83
# if !defined(B_ENDIAN)
sl@0
    84
/*
sl@0
    85
 * *_block_host_order is expected to handle aligned data while
sl@0
    86
 * *_block_data_order - unaligned. As algorithm and host (x86)
sl@0
    87
 * are in this case of the same "endianness" these two are
sl@0
    88
 * otherwise indistinguishable. But normally you don't want to
sl@0
    89
 * call the same function because unaligned access in places
sl@0
    90
 * where alignment is expected is usually a "Bad Thing". Indeed,
sl@0
    91
 * on RISCs you get punished with BUS ERROR signal or *severe*
sl@0
    92
 * performance degradation. Intel CPUs are in turn perfectly
sl@0
    93
 * capable of loading unaligned data without such drastic side
sl@0
    94
 * effect. Yes, they say it's slower than aligned load, but no
sl@0
    95
 * exception is generated and therefore performance degradation
sl@0
    96
 * is *incomparable* with RISCs. What we should weight here is
sl@0
    97
 * costs of unaligned access against costs of aligning data.
sl@0
    98
 * According to my measurements allowing unaligned access results
sl@0
    99
 * in ~9% performance improvement on Pentium II operating at
sl@0
   100
 * 266MHz. I won't be surprised if the difference will be higher
sl@0
   101
 * on faster systems:-)
sl@0
   102
 *
sl@0
   103
 *				<appro@fy.chalmers.se>
sl@0
   104
 */
sl@0
   105
# define md5_block_data_order md5_block_host_order
sl@0
   106
# endif
sl@0
   107
#endif
sl@0
   108
sl@0
   109
#define DATA_ORDER_IS_LITTLE_ENDIAN
sl@0
   110
sl@0
   111
#define HASH_LONG		MD5_LONG
sl@0
   112
#define HASH_LONG_LOG2		MD5_LONG_LOG2
sl@0
   113
#define HASH_CTX		MD5_CTX
sl@0
   114
#define HASH_CBLOCK		MD5_CBLOCK
sl@0
   115
#define HASH_LBLOCK		MD5_LBLOCK
sl@0
   116
#define HASH_UPDATE		MD5_Update
sl@0
   117
#define HASH_TRANSFORM		MD5_Transform
sl@0
   118
#define HASH_FINAL		MD5_Final
sl@0
   119
#define	HASH_MAKE_STRING(c,s)	do {	\
sl@0
   120
	unsigned long ll;		\
sl@0
   121
	ll=(c)->A; HOST_l2c(ll,(s));	\
sl@0
   122
	ll=(c)->B; HOST_l2c(ll,(s));	\
sl@0
   123
	ll=(c)->C; HOST_l2c(ll,(s));	\
sl@0
   124
	ll=(c)->D; HOST_l2c(ll,(s));	\
sl@0
   125
	} while (0)
sl@0
   126
#define HASH_BLOCK_HOST_ORDER	md5_block_host_order
sl@0
   127
#if !defined(L_ENDIAN) || defined(md5_block_data_order)
sl@0
   128
#define	HASH_BLOCK_DATA_ORDER	md5_block_data_order
sl@0
   129
/*
sl@0
   130
 * Little-endians (Intel and Alpha) feel better without this.
sl@0
   131
 * It looks like memcpy does better job than generic
sl@0
   132
 * md5_block_data_order on copying-n-aligning input data.
sl@0
   133
 * But frankly speaking I didn't expect such result on Alpha.
sl@0
   134
 * On the other hand I've got this with egcs-1.0.2 and if
sl@0
   135
 * program is compiled with another (better?) compiler it
sl@0
   136
 * might turn out other way around.
sl@0
   137
 *
sl@0
   138
 *				<appro@fy.chalmers.se>
sl@0
   139
 */
sl@0
   140
#endif
sl@0
   141
sl@0
   142
#include "md32_common.h"
sl@0
   143
sl@0
   144
/*
sl@0
   145
#define	F(x,y,z)	(((x) & (y))  |  ((~(x)) & (z)))
sl@0
   146
#define	G(x,y,z)	(((x) & (z))  |  ((y) & (~(z))))
sl@0
   147
*/
sl@0
   148
sl@0
   149
/* As pointed out by Wei Dai <weidai@eskimo.com>, the above can be
sl@0
   150
 * simplified to the code below.  Wei attributes these optimizations
sl@0
   151
 * to Peter Gutmann's SHS code, and he attributes it to Rich Schroeppel.
sl@0
   152
 */
sl@0
   153
#define	F(b,c,d)	((((c) ^ (d)) & (b)) ^ (d))
sl@0
   154
#define	G(b,c,d)	((((b) ^ (c)) & (d)) ^ (c))
sl@0
   155
#define	H(b,c,d)	((b) ^ (c) ^ (d))
sl@0
   156
#define	I(b,c,d)	(((~(d)) | (b)) ^ (c))
sl@0
   157
sl@0
   158
#define R0(a,b,c,d,k,s,t) { \
sl@0
   159
	a+=((k)+(t)+F((b),(c),(d))); \
sl@0
   160
	a=ROTATE(a,s); \
sl@0
   161
	a+=b; };\
sl@0
   162
sl@0
   163
#define R1(a,b,c,d,k,s,t) { \
sl@0
   164
	a+=((k)+(t)+G((b),(c),(d))); \
sl@0
   165
	a=ROTATE(a,s); \
sl@0
   166
	a+=b; };
sl@0
   167
sl@0
   168
#define R2(a,b,c,d,k,s,t) { \
sl@0
   169
	a+=((k)+(t)+H((b),(c),(d))); \
sl@0
   170
	a=ROTATE(a,s); \
sl@0
   171
	a+=b; };
sl@0
   172
sl@0
   173
#define R3(a,b,c,d,k,s,t) { \
sl@0
   174
	a+=((k)+(t)+I((b),(c),(d))); \
sl@0
   175
	a=ROTATE(a,s); \
sl@0
   176
	a+=b; };