| ??? 01/24/03 16:22 Read: times |
#37110 - volatile keyword and not-so-optimizer |
I checked the use of 'volatile' declarations both on IAR and Tasking at different levels of otimization. Apparently, even if the code could be dumped, both compilers do leave it intact so I guess that 'volatile' merely instructs the optimizer to leave the variable untouched. Not-so-optimizer ? |
| Topic | Author | Date |
| volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
| RE: volatile keyword | 01/01/70 00:00 | |
volatile keyword and not-so-optimizer | 01/01/70 00:00 |