Post Reply 
WP-34S: Safely copy a graphics register's contents
06-11-2014, 10:17 PM
Post: #11
RE: WP-34S: Safely copy a graphics register's contents
(06-11-2014 10:11 PM)Paul Dale Wrote:  
(06-11-2014 10:01 PM)Dave Britten Wrote:  Ah, R-COPY should be the secret ingredient I need. Currently the program happens to be running in BASE 10 64-bit word size when it does the STO/RCL, so it appears to work fine, but I'll change it to the safer method. Looks like I just need to call 1.01 R-COPY to do the job.

You should be safe in 64 bit integer mode. Masking off the unused bits here won't change anything. The sign mode shouldn't matter but unsigned would be safest.

The base is display only so that won't impact the contents.

1.01 R-COPY can be written as # 101 SDR 002 R-COPY. This will save a couple of steps and be faster.

- Pauli

Okay, good to know about using unsigned mode. That makes more sense for this program anyway.

I think I'm going to stick with STO/RCL and make sure I'm running 64-bit unsigned. I realized have a need to compare the two register values to see if there's a change, and I'll need to get them onto the stack unmangled anyway in order to do that, so might as well just STO after I'm done comparing.

Thanks for the input guys.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 

Messages In This Thread
RE: WP-34S: Safely copy a graphics register's contents - Dave Britten - 06-11-2014 10:17 PM

User(s) browsing this thread: 1 Guest(s)