| ??? 11/02/09 10:52 Read: times |
#170332 - Hmm. Even odder. Responding to: ???'s previous message |
There's another odd thing that I've just noticed. If I step through the code up to the line
Reload_16 = (tWord) (65536UL - Inc); before that line TICK_MS has a value of 0x10, but after that line TICK_MS has a value of 0xF0. Why would that line change TICK_MS? |
| Topic | Author | Date |
| Odd calculation result... | 01/01/70 00:00 | |
| Hmm. Even odder. | 01/01/70 00:00 | |
| what is the definition... | 01/01/70 00:00 | |
| Compiler reuses registers and memory cells | 01/01/70 00:00 | |
| Ah. | 01/01/70 00:00 | |
| Disable compiler optimizations. | 01/01/70 00:00 | |
| Compiler bug? | 01/01/70 00:00 | |
| Maturity of compilers | 01/01/70 00:00 | |
| the primary suspect should always be the end user. | 01/01/70 00:00 | |
| "innovation" as alternative name for bug | 01/01/70 00:00 | |
| C51 also does that! | 01/01/70 00:00 | |
| C51 has smart linker | 01/01/70 00:00 | |
| I found a some genuine compiler bugs. | 01/01/70 00:00 | |
| Broken code in RTL is the worst | 01/01/70 00:00 | |
| Thanks! | 01/01/70 00:00 | |
| Defs | 01/01/70 00:00 | |
| poor choice of names | 01/01/70 00:00 | |
| Good data types are really critical | 01/01/70 00:00 | |
| I'm an idiot. | 01/01/70 00:00 | |
| informative! | 01/01/70 00:00 | |
| "Answer is wrong" | 01/01/70 00:00 | |
Which one would you prefer?? | 01/01/70 00:00 |