@hwnd%

[Ric]

I now have my basic terrain rendering program working in BBCSDL32. Thankyou Richard. Starting to convert to BBCSDL64 has thrown up quite a few errors, so ill start with the first.

Code: Select all

 
 3522 DIM code%% NOTEND AND 2047, code%% (2048*40)-1
 3523 DIM ]^O% 2048, ]^L% -1
 3524 ]^P% = code%%
 3525 FOR I% = 0 TO 2 STEP 2
 3526
 3527   [
 3528   opt I%
 3529
 3530   .float4_to_8
 3531
 3532   fld              DWORD [float4]

Not sure about the DIM statements and what they do, but it syntax errors at line 3532.

[Richard Russell]

it syntax errors at line 3532.

Code: Select all

 
 3532   fld              DWORD [float4]

I'm no expert in 64-bit assembly language, but my understanding is that the memory operand can't be an absolute address (pointer), because it would require 8 bytes; very few instructions can take an 8-byte absolute address for the same reason. What you have to use instead is a relative address, which needs only four bytes - the same number as the absolute address would in 32-bit code:

Code: Select all

 
 3532   fld              DWORD [rel float4]

I discussed earlier in the thread the technique of using relative pointers rather than absolute ones, to keep the size as 32-bits, and this is an example of the CPU itself adopting the same strategy.

[Ric]

Could you please confirm whether this code is correct. At the moment i am only trying to compile two lines of asm.

Code: Select all

3522 DIM code%% NOTEND AND 2047, code%% 2048
 3523 DIM ]^O% 2048, ]^L% -1
 3524 ]^P% = code%%
 

I have copied it from the differences in x64, sort of!
I have looked back through the thread to where you mention pointers/relative address, but i dont understand what they are.
I've tried all of these

Code: Select all

fld DWORD [rel float4]
fld rel DWORD [float4]
fld DWORD PTR [float4]
fldDWORD_PTR [float4]

fld DWORD PTR [float4] gives the error "missing #", the rest cause a syntax error.
How does relative addressing work?