mldonkey-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Mldonkey-users] [patch #4657] Improve endianness checking in tiger.c, m


From: spiralvoice
Subject: [Mldonkey-users] [patch #4657] Improve endianness checking in tiger.c, m5_c.c and CryptoPP.h
Date: Mon, 28 Nov 2005 17:02:54 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; de-DE; rv:1.7.12) Gecko/20051125 Firefox/1.0.7

URL:
  <http://savannah.nongnu.org/patch/?func=detailitem&item_id=4657>

                 Summary: Improve endianness checking in tiger.c, m5_c.c and
CryptoPP.h
                 Project: mldonkey, a multi-networks file-sharing client
            Submitted by: spiralvoice
            Submitted on: Mo 28.11.2005 um 17:02
                Category: Bug fixes
                Priority: 9 - Immediate
                  Status: None
             Assigned to: None
        Originator Email: 
             Open/Closed: Open

    _______________________________________________________

Details:

./configure checks endianness, until now this was only used in
sha1 C code.
tiger.c and md5_c.c had their own (incomplete) ways of checking endianness,
see bug #14664 for problems on 64bit little
endian machines which IMHO are assumed big endian.

This patch promises to solve this bug, the endianness check code
from sha1_new_c.c has been moved to endian_check.h so it can be
re-used by sha1_new_c.c, tiger.c, md5_c.c and CryptoPP.h.





    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Mo 28.11.2005 um 17:02  Name: endian.patch  Size: 14,69KB   By:
spiralvoice

<http://savannah.nongnu.org/patch/download.php?item_id=4657&item_file_id=5523>

    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/patch/?func=detailitem&item_id=4657>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.nongnu.org/





reply via email to

[Prev in Thread] Current Thread [Next in Thread]