1. 21 11月, 2004 1 次提交
    • A
      RC4 tune-up for Intel P4 core, both 32- and 64-bit ones. As it's · 376729e1
      Andy Polyakov 提交于
      apparently impossible to compose blended code with would perform
      satisfactory on all x86 and x86_64 cores, an extra RC4_CHAR
      code-path is introduced and P4 core is detected at run-time. This
      way we keep original performance on non-P4 implementations and
      turbo-charge P4 performance by factor of 2.8x (on 32-bit core).
      376729e1
  2. 18 11月, 2004 1 次提交
  3. 17 11月, 2004 3 次提交
  4. 16 11月, 2004 1 次提交
  5. 14 11月, 2004 4 次提交
  6. 13 11月, 2004 2 次提交
  7. 12 11月, 2004 3 次提交
  8. 11 11月, 2004 2 次提交
  9. 10 11月, 2004 1 次提交
  10. 05 11月, 2004 1 次提交
  11. 03 11月, 2004 1 次提交
  12. 02 11月, 2004 1 次提交
    • R
      Because -rpath/-R may have been used, our settings of LD_LIBRARY_PATH · ffd0f93f
      Richard Levitte 提交于
      and friends may be entirely useless.  In such a case, LD_PRELOAD is
      the answer, at least on platforms using LD_LIBRARY_PATH.  There might
      be other variables to set on other platforms, please fill us in...
      
      For now, we only do this with the tests, so they won't fail for silly
      reasons like getting dynamically linked to older installed libraries
      rather than the newly built ones...
      
      PR: 960
      ffd0f93f
  13. 01 11月, 2004 1 次提交
  14. 26 10月, 2004 1 次提交
  15. 25 10月, 2004 2 次提交
  16. 21 10月, 2004 1 次提交
  17. 14 10月, 2004 1 次提交
  18. 05 10月, 2004 2 次提交
  19. 01 10月, 2004 2 次提交
  20. 29 9月, 2004 1 次提交
  21. 28 9月, 2004 2 次提交
  22. 27 9月, 2004 2 次提交
  23. 25 9月, 2004 1 次提交
  24. 24 9月, 2004 1 次提交
    • R
      Import changed files from LPlib. The changes are logged as follows · bb09fd2b
      Richard Levitte 提交于
      for LPdir_unix.c in LPlib.  For the other files, only the last log
      entry applies.
      
      ----------------------------
      revision 1.11
      date: 2004/09/23 22:07:22;  author: _cvs_levitte;  state: Exp;  lines: +20 -6
      Define my own macro LP_ENTRY_SIZE to express the size of my own
      buffering of directory entries, and make it depend on whichever comes
      first of PATH_MAX and NAME_MAX.  As a fallback, make sure it's set to
      255 if neither PATH_MAX or NAME_MAX were defined.  Also, if the size
      given from PATH_MAX or NAME_MAX is less than 255, force LP_ENTRY_SIZE
      to be 255.
      
      It makes no harm whatsoever if LP_ENTRY_SIZE is larger than the
      maximum local path name limit.  It does make a lot of harm if
      LP_ENTRY_SIZE is smaller.  255 seemed like a fairly acceptable default
      when nothing else is available.
      ----------------------------
      revision 1.10
      date: 2004/08/26 13:36:05;  author: _cvs_levitte;  state: Exp;  lines: +13 -13
      License correction.  I am not REGENTS, just a COPYRIGHT HOLDER.
      ----------------------------
      bb09fd2b
  25. 19 9月, 2004 2 次提交