Moshin wrote:
> I guess your bcc compiler is using this typedef in sha2.h:72 for
> unsigned 64bit long:
>
> typedef unsigned long long sha2_64t;
>
> and then it has problems with 'long long'; to fix this
> add an ifdef for your compiler and a defn for sha2_64t
> in sha2.h in here:
>
> /* define an unsigned 64-bit type */
>
> #if defined( _MSC_VER )
> typedef unsigned __int64 sha2_64t;
> #define s_u64 ui64
> #elif ULONG_MAX =3D=3D 0xffffffffffffffff
> typedef unsigned long sha2_64t;
> #define s_u64 ul
> #elif ULONG_MAX =3D=3D 0xffffffff
> typedef unsigned long long sha2_64t; /* a somewhat dangerous guess */
> #define s_u64 ull
> #else
> #error Please define sha2_64t as an unsigned 64 bit type in sha2.h
> #endif
For Unix systems we should use configure to find a 64 bit type.
Nevertheless, there will be systems without support for a 64 bit type.
Can you change the code to use a 32 bit type? If that is inefficient,
using #ifdef to only use 32 bit when no 64 bit type is available would
be good. However, I expect 64 bit systems to be able to deal with 32
bit efficiently.
--
ARTHUR: No, hang on! Just answer the five questions ...
GALAHAD: Three questions ...
ARTHUR: Three questions ... And we shall watch ... and pray.
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
To unsubscribe from this group, send email to
vim_dev+unsubscribegooglegroups.com or reply to this email with the words
"REMOVE ME" as the subject.
