 |
forums.silverfrost.com Welcome to the Silverfrost forums
|
View previous topic :: View next topic |
Author |
Message |
wahorger

Joined: 13 Oct 2014 Posts: 927 Location: Morrison, CO, USA
|
Posted: Sat Jan 23, 2021 5:07 pm Post subject: |
|
|
Robert, yes, this is a side effect of memory being filled with spaces, incorrectly, wiping out local variables, and constants that would nominally be correct for error-free operation. The reason for this is mystifying especially since I did a test where none of my code was run, yet local variables did not have their set values (via a DATA statement).
I am no longer concerned about LENG8$, it is operating correctly if given correct inputs. In this case, it was not. |
|
Back to top |
|
 |
mecej4
Joined: 31 Oct 2006 Posts: 1469
|
Posted: Sat Jan 23, 2021 5:08 pm Post subject: |
|
|
Robert wrote: "It isn't byte 0x20 repeated, it is 0x02 repeated".
The index variable I_LOGMTR pertains to character*16 variables. The instructions
MOVSX_Q RBX,I_LOGMTR
IMUL_Q RBX,16_4
cause RBX to contain I_LOGMTR shifted left by one nybble, before the call to LENG8$, and the function does not touch RBX. |
|
Back to top |
|
 |
Robert

Joined: 29 Nov 2006 Posts: 374 Location: Manchester
|
Posted: Sat Jan 23, 2021 5:15 pm Post subject: |
|
|
Ah, I see. |
|
Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|