PureBasic Forums - English

Ok, but only because I'm the starting author.
No questions to C-Backend!

;- https://www.intel.com/content/www/us/en/developer/articles/technical/intel-sha-extensions.html
;- PureBasic 6.02 LTS (x64), ASM-Backend
;- Source for this Test: Unicode String
;- SH1 is unsave (broken)!

;Check for CPU-SHA ...

@chi:

Procedure BitmapFillColor(Width.l, Height.l, ARGB.l=$FF000000)
Protected img.l, bmi.BITMAPINFO
bmi\bmiHeader\biSize = SizeOf(BITMAPINFOHEADER)
bmi\bmiHeader\biWidth = Width
bmi\bmiHeader\biHeight = -Height
bmi\bmiHeader\biPlanes = 1
bmi\bmiHeader\biBitCount = 32
img = CreateDIBSection ...

For instructions like STOSD it´s a good idea set/clear explicit the Direction Flag before. In this case

Padding in PB are not fix values. The last Block is internal expanded with the last Bytes of the Block before.
This is a simple example:

;No Unicode!!!

String$ = "Hello this is a test for AES"
Debug String$
Debug "Len: " + Len(String$) ;28, we need 32
*CipheredString = AllocateMemory(Len(String ...

I´m a fan of Mersenne-Primes and other big numbers and the calculation of this.
My code for this with use of FFT:

;- Fast Unsigned FFT-Integer-Multiplication
;- see https://en.wikipedia.org/wiki/Butterfly_diagram (radix-2 decimation-in-time FFT algorithm)
;- FFT-Multplication in PureBasic see ...

Corona: No pubs, no bars... Much time for program -> corrected version (physical register):

Procedure FPU(FPU_ID)
Protected.q SaveRam, SaveRamAli, C1, PhysReg, RFlags, CW, SW, Tags
Protected.d FST0, FST1, FST2, FST3, FST4, FST5, FST6, FST7
Protected.s sN = "Clear", sY = "Set", sSW = "S E T ...

PureBasic don´t use FPU-instructions, it uses the msvcrt.dll (routines without FPU).

With this you can check the FPU-Registers:


Procedure FPU()
Global.q SaveRam, SaveRamAli, Ali
Global.d FST0, FST1, FST2, FST3, FST4, FST5, FST6, FST7
Global Tag.b
Protected Tag0$=" Free", Tag1$=" Free", Tag2$=" Free", Tag3$=" Free", Tag4$=" Free", Tag5$=" Free", Tag6$=" Free", Tag7$=" Free ...

Code part2:

Procedure wc(hWnd, uMsg, wParam, lParam) ;WindowCallback, nur für Stellungseingabe!
Select uMsg
Case #WM_LBUTTONUP
MX = WindowMouseX(0)
MY = WindowMouseY(0)
If MX > 20 And MX < 340 ;Vergleiche ohne "=" !
MX - 20
MX / 40
Maus_Linie = MX + 97 ;97="a"
If MY > ORand And MY ...

For tests (analysis) and fun I wrote this (is under construction!) for the asmFishW-engines:
Code part1:

;Helles asmFishW-Player, 7.Oct.2019
;For asmFishW!
;PB 5.70 LTS (x64)
;UNICODE!

;UNDER CONSTRUCTION!
;No move-check!!!
;No table-bases
;No ponderhit
;No ...
;German

;Download asmFishW-Engines ...

You can use for Windows x64 the msvcrt.dll (PB use this DLL for many purposes):

;Windows x64
If OpenLibrary(0, "msvcrt.dll")
Prototype.q Abs64(V1.q)
Prototype.l Abs32(V2.l)
Abs64.Abs64 = GetFunction(0, "_abs64")
Abs32.Abs32 = GetFunction(0, "labs")
CloseLibrary(0)
Else
;Error
EndIf

y1.q ...

For fun with FPU, SSE and SSE2; PB 64-bit:

;PB 5.61 (x64)
Procedure.s DMS_FPU(DD.d)
!fstcw word[CW_FPU]
!mov ax,[CW_FPU]
!or [CW_FPU],0000110000000000b ;no rounding, truncation
!fldcw word[CW_FPU]

!fld qword[p.v_DD] ;no check of range!
!fist word[DMS_FPU]
!fisub word[DMS_FPU]
!fmul qword ...

The PDH.dll is language-sensitive! For the german-version replace in the procedure with

What´s your hardware? I have for fun a FTDI UM232H and a LED-strip WS2801. This is code for tests and a "running light", 64-bit-version (no problem to convert in 32, comments in german):

OutputBuffer.q
OutputBuffer1.q ;für "schwarz"
InputBuffer.q
ftHandle.l
NumBytesToSend.l
NumBytesRead.l ...

Sorry, but if I install a new PB-version, first action is copy the latest FAsm-version into the PB Compilers-Directory.
SHA-support is new in FAsm-version 1.71.40 (Oct 19, 2015)! 2 years !