- 02 8月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
going out...
-
- 01 8月, 2004 1 次提交
-
-
由 Andy Polyakov 提交于
if we explicitly intruct the linker to set entry point, then we become obliged to initialize run-time library. Instead we can pick name run-time will call and such name is DllMain. Note that this applies to both "native" Win32 environment and Cygwin:-)
-
- 30 7月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
-
- 27 7月, 2004 5 次提交
-
-
由 Richard Levitte 提交于
static variable
-
由 Dr. Stephen Henson 提交于
-
由 Dr. Stephen Henson 提交于
-
由 Andy Polyakov 提交于
http://cvs.openssl.org/chngview?cn=12493. Now all platform should be operational, while SSE2 code pathes get engaged on ELF platforms only.
-
由 Andy Polyakov 提交于
is to have a placeholder to small routines, which can be written only in assembler. In IA-32 case this includes processor capability identification and access to Time-Stamp Counter. As discussed earlier OPENSSL_ia32cap is introduced to control recently added SSE2 code pathes (see docs/crypto/OPENSSL_ia32cap.pod). For the moment the code is operational on ELF platforms only. I haven't checked it yet, but I have all reasons to believe that Windows build should fail to link too. I'll be looking into it shortly...
-
- 26 7月, 2004 11 次提交
-
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
stop complaining about loss of precision, but explicit cast.
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
because "wrong" casts will either be optimized away or never performed.
-
- 24 7月, 2004 7 次提交
-
-
由 Andy Polyakov 提交于
libraries. Old .sl extension works just fine, but it .so which is default.
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
Win64 comes in two flavors, IA-64/Itanium and AMD64/Opteron. The suggestion is to refer to former as WIN64I and latter - WIN64A
-
由 Andy Polyakov 提交于
-
- 23 7月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
Apparently, the length *including* the NUL byte should be used. Contributed by Andy Polyakov <appro@fy.chalmers.se>
-
- 22 7月, 2004 8 次提交
-
-
由 Richard Levitte 提交于
Make a nicer comment, as we don't really know for sure that it's really needed, and just want to play on the safe side. Suggest by Andy Polyakov <appro@fy.chalmers.se>
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
with HP-UX offering 14 for NAME_MAX?
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
SIXTY_FOUR_BIT_LONG) were failing to pass 'cd test; make test_bn'.
-
由 Richard Levitte 提交于
Some code beautification. Change the macro CP_THREAD_ACP to CP_ACP, because the latter is more widely defined. Add a conditional macro definition in case FindFirstFile and FindNextFile aren't properly defined (might happen on WinCE). Suggested by Andy Polyakov <appro@fy.chalmers.se>
-
由 Andy Polyakov 提交于
-
- 21 7月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
Windows changes that detects if multibyte characters are available and deals with them properly. Contributed by Andy Polyakov <appro@fy.chalmers.se>
-
- 20 7月, 2004 1 次提交
-
-
由 Richard Levitte 提交于
NUL-teminated at all times, and that we don't make unneeded calls to free().
-
- 19 7月, 2004 3 次提交
-
-
由 Richard Levitte 提交于
instead of local time.
-
由 Andy Polyakov 提交于
-
由 Andy Polyakov 提交于
-