Subject:
|
Further Adventures with Assembler
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 27 Jan 2004 03:12:37 GMT
|
Viewed:
|
4028 times
|
| |
|
|
Just wanted to thank everyone again for the help on assembler. I've been very
successful and managed to greatly increase the speed of a critical portion of my
program. However, I'm still having a very bizarre issue:
In the middle of an assember block, there's an instruction that moves a value
from an array into a register:
mov.b @(_myglobalarray, r3), r5
The code compiles fine. But when I copy this line exactly and place it again at
the end of the assembler block and compile (for the next segment of an analysis
process), suddenly BOTH lines trigger an error.
The same error is triggered by commenting out normal blocks of c++ code that are
below the return 0 statement. These are commands that are never executed!
Anyone have any insight into how these can be prevented/worked around? I feel it
must be some sort of compiler peculiarity that I just need to be made aware
of... either way, it's two things I want to do which are both producing the same
strange symptom.
Thanks again,
Mike
|
|
Message has 1 Reply:
 | | Re: Further Adventures with Assembler
|
| (...) The line above should produce an error because you are specifying a byte move into a word register. The fact that it doesn't always cause an error makes me think there's something flakey (in the assembler) in the way instruction operand sizes (...) (20 years ago, 27-Jan-04, to lugnet.robotics.rcx.legos)
|
4 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
