| ??? 07/12/07 18:27 Read: times |
#141824 - volatile Responding to: ???'s previous message |
Making Ralph volatile should have solved your problem. First it is required already because Ralph can be changed from outside the normal control flow (in the ISR) and must not be optimized, but read every time. But secondly if your C statement reads the variable only once (which it does), the generated code may not read it more often. |
| Topic | Author | Date |
| more to atomicity and such | 01/01/70 00:00 | |
| Interesting example ... | 01/01/70 00:00 | |
| which I did | 01/01/70 00:00 | |
| Aside: Keil - Atomic functions | 01/01/70 00:00 | |
| If you can afford it. | 01/01/70 00:00 | |
| volatile | 01/01/70 00:00 | |
| does this have some formal definition? | 01/01/70 00:00 | |
| sequence points and side effects | 01/01/70 00:00 | |
| what's exactly the value of volatile, then? | 01/01/70 00:00 | |
| example | 01/01/70 00:00 | |
| bu what is it good for then? | 01/01/70 00:00 | |
| Ok, visualize this one | 01/01/70 00:00 | |
| within a loop | 01/01/70 00:00 | |
| Memory Mapped I/O | 01/01/70 00:00 | |
OK I see it now, thanks. | 01/01/70 00:00 | |
| volatile switch | 01/01/70 00:00 |