| ??? 03/27/01 14:04 Read: times |
#10347 - RE: Too many falg bits in the code |
"I have to define too many flag bits in the RAM to be used during execution."
Are you saying that the 256 flags between 20 and 2F are not enough? as to the next 2 queastions A method I have used twice (that's not very often for me) is to use a bitbyte as flags. Load the flagbyte in the acc and a movc dptr+a to fetch the offset in a table used to do a jmp a+dptr. This method really speed things up when many bits are involved in a decision and may save code size. Have you tried state machines, they tend to create an organized handling of many variables. To squeeze a few bytes out of ROM what do you do? I wish there was a general answer. For you maybe the method would be to organize the bits in a decision into one bitbyte e.g. 023h load taht byte and xor the bits that must be one, the a jz will take care of all your decisions. Hope this is helpful, but remember whether you squeeze it into a smaller rom or not - have fun Erik |
| Topic | Author | Date |
| Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many flag bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
| RE: Too many falg bits in the code | 01/01/70 00:00 | |
RE: Too many falg bits in the code | 01/01/70 00:00 |