David Kelly wrote: > Volatile informs the compiler that > the object may change between the > compiler's uses ... And when changing > the value it must write it out > immediately. And not merge the access > across multiple statements. then, Robert Adsett wrote: > What it actually means though is that > access to a volatile variable must > take place in the order they are > specified and exactly as many times > as is specified. But, that exactly what David wrote! Graham.
Message
Re: AvrStudio4 (2008), WinAVR (2007-05...) and Dragon problem debugging C code (jtag)
2008-06-09 by Graham Davies