-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
faults when compiled with cygwin(64bit) #5
Comments
The WIN64 part is due to different register preservation and argument passing on Windows and UNIX. I'm not familiar how Cygwin manages this part, but it's possible that it needs not -DWIN64 at all. |
without -DWIN64 the program faults immediately, i believe cygwin64 uses microsoft conventions for register/function usage, only thing to watch out for below is ugly, because i had to use 'code' indicators to get the double underscores to show up,
|
Does it work if compiled in the 32-bit mode? |
yes, i just got that yesterday. (i had to install cygwin32 to coexist on my system and figure out the magic incantation.) here is my modified build.sh scrypt if you want to see if i've done anything completely bone headed. #!/bin/sh grepout= echo "$CC $CFLAGS $DEFINES -c neoscrypt.c" echo "$CC $CFLAGS $DEFINES -c neoscrypt_test.c" echo "$CC $DEFINES -c neoscrypt_asm.S" echo "$LD |
hi there!
i compiled this (with -DWIN64) under windows7 cygwin-64bit
it runs okay up to NeoScrypt SSE2 4-way part D integrity test passing.
but when it moves on to Scrypt SSE2 4-way part A the program faults.
i'm by no means an assember guy :) but do the Scrypt assembler routines
still need their entry sequences WIN64-izing ?
--ken
The text was updated successfully, but these errors were encountered: