Reply to post: Re: Not just assembly.

Can your rival fix it as fast? turns out to be ten-million-dollar question for plucky support guy

swm

Re: Not just assembly.

This used to be a technique to get more memory by using constants as variables.

On the IBM 1620 FORTRAN copying from an uninitialized variable could cause memory to be cleared as the uninitialized variable had no "flag" indicating "end of number".

On the SIGMA 7 you could intersperse machine instructions in your FORTRAN code. I once wondered why why a SW instruction (Store Word) wasn't changing memory until I realized the opcode was STW.

Finding your own bugs is hard.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon