forked from miracl/MIRACL
-
Notifications
You must be signed in to change notification settings - Fork 0
/
problems.txt
87 lines (66 loc) · 4.01 KB
/
problems.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
MIRACL - Bug warnings
The MIRACL library is written in standard C and has been tested on many
combinations of computer and compiler. It should work on any system which
supports C as defined by Kernighan and Richie. The author is interested to
hear of any problems that arise with other configurations.
**** NOTE: If upgrading an old version of MIRACL, make sure to replace all old
files with new ones. In particular make sure to replace headers, such as
MIRACL.H. Newer versions of this header may have extensions to the "miracl"
structure. If an old MIRACL.H header is inadvertently used, the offsets
within this structure will be wrong, and all sorts of obscure run-time errors
will ensue.
Remember - not all compilers are perfect! MIRACL already contains work-
arounds which were necessary to circumvent bugs in certain compilers.
Some of the routines in MIRACL stretch a compiler's completeness to
the limit.
Some drastic bugs, however, cannot be avoided.
For example the early Microsoft C Version 5.0 (not to be confused with the
current C++ compiler), sometimes got the wrong
answer when dividing two unsigned longs. For example try dividing 4294967167
by 71583361. It gets 60. The correct answer is 59. This problem makes it
impossible to use a full-width base using this compiler with 'mr_utypes' defined
as 'long'. This problem was fixed in version 5.1 (but think of
Star Wars - the Strategic Defence Initiative - and worry).
Other possible problems:
Remember that the example programs must be linked to a pre-compiled MIRACL
library, so that the MIRACL routines can be incorporated into the executables.
Most 32-bit compilers now support a 64-bit type. But unfortunately some call
it "long long", while others call it "__int64". Make sure the right name is
used in mirdef.h
C programs need only be linked to the MIRACL library.
But note that C++ programs need also to be linked to at least one or more of
the object files created by compiling big.cpp, zzn.cpp, crt.cpp,
ecn.cpp or flash.cpp. See the xxDOIT.BAT files for examples.
When using RATCALC.EXE on an IBM PC or compatible, be sure to set up your
system to use US Code Page 437, otherwise certain graphics characters will
appear incorrectly on the screen. See your DOS documentation for details.
Remember to include stdio.h BEFORE including miracl.h in your C programs.
Similarly include I/O libraries before big.h, number.h or flash.h in C++
programs. This is important as certain types (such as FILE *) need to be
defined before the MIRACL headers are included.
Most user problems arise due to building the MIRACL library with the wrong
MIRDEF.H file, or by inclusion of the wrong assembly language routines
from mrmuldv.any. Be careful. Only use MIRDEF.H32 if you have both a true 32-
bit CPU *AND* a true 32-bit compiler.
The "fast" code for modular arithmetic is NOT included in
the precompiled libraries. To use this code the individual module e.g.
mrkcm.c must be seperately created using the mex utility, compiled and linked
in. Note also that only one of these methods can be used at a time.
Whenever possible use config.c to generate a valid MIRDEF.H
Early versions of the GCC compiler did not seem to like the generated mrcomba.c and
mrkcm.c files. If it objects switch off optimization - the inline assembly is
optimized enough. Or try -fomit-frame-pointer
If using MIRACL on a computer which does not support a
fullwidth number base, remember to (a) #define MR_NOFULLWIDTH in
mirdef.h, and (b) use mirsys(...,MAXBASE) instead of mirsys(...,0) in all
your programs.
Try using the config.c program to automatically generate a mirdef.h
file for you.
If you have any other problems with MIRACL, please let us know. Email to
mscott@indigo.ie
DISCLAIMER
In no event will the Authors be liable to you for any damages, including
any lost profits, lost savings or other incidental or consequential
damages arising out of the use of or inability to use these programs,
even if the Authors have been advised of the possibility of such damages,
or for any claim by any other party.