wz/if_z not doing what I expect

Given this code:
DAT
              ...

              mov test_reg, test_value          wz
        if_z  mov wait_time, long_wait_time

              ...

long_wait_time          long    $C000000
short_wait_time         long    $A00000
wait_time               res     4    
wait_reg                res     4
test_value              long    $FFFF_FFFF
test_reg                res     4


The line that begins with "if_z" shouldn't execute, right? When I run the code, it does. The complete program is attached. if I replace "test_value" in the excerpt above with "#1", the line that begins with "if_z" (as expected) doesn't execute.

What I think is happening is that the mov statement above moves the value $FFFF_FFFF into test_reg. Where am I going wrong?

▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
OS-X: because making Unix user-friendly was easier than debugging Windows
OS-X: because making Unix user-friendly was easier than debugging Windows

My band's website
Our first album on the iTunes Store
Ryer Island: our second album...
Tagged:

Comments

  • 4 Comments sorted by Votes Date Added
  • CJCJ
    edited June 2006 Posts: 0Vote Up0Vote Down
    all of the predefined data, needs to be before the reserved space, the modified code is attached

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Who says you have to have knowledge to use it?

    I've killed a fly with my bare mind.
  • edited June 2006 Posts: 0Vote Up0Vote Down
    Steve,
    · I had made the same mistake, and couldn't figure it out either.
    · Look through the "Tricks & Traps" document, it has alot of good info.
    Bean.

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    Cheap 4-digit LED display with driver IC·www.hc4led.com


    COMING SOON "SD DATA LOGGER" www.sddatalogger.com

    "I reject your reality, and substitute my own." Mythbusters
    ·
    logo.png?503
    Esterline Research & Design
    thitt@esterlineresearch.com

    We offer consulting on the following areas of expertise:
    Frequency Control - Micro-Controller/Processor Projects
    Test and Automation - General Programming and Coding
    Circuit Design - Board Layouts
  • edited June 2006 Posts: 808Vote Up0Vote Down
    Thanks, CJ & Bean. I don't know how I managed to miss the Tricks & Traps document. I guess that was before I started reading the Propeller thread. What a life saver! I already managed to learn two of the Tricks the hard way. smile.gif

    ▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔▔
    OS-X: because making Unix user-friendly was easier than debugging Windows
    OS-X: because making Unix user-friendly was easier than debugging Windows

    My band's website
    Our first album on the iTunes Store
    Ryer Island: our second album...
Sign In or Register to comment.