search for: msg00242

...he situation under MSVC++ [1]. GCC's interpretation of volatile is for memory mapped hardware, so it does not allow me to use the qualifier to tame the optimizer [2]. Jeff [1] http://msdn.microsoft.com/en-us/library/vstudio/12a04hfd%28v=vs.90%29.aspx [2] http://gcc.gnu.org/ml/gcc-help/2012-03/msg00242.html

On Mon, Jun 17, 2013 at 10:29 AM, Jeffrey Walton <noloader at gmail.com> wrote: > > > First is to ensure dead-writes are not removed. For example, a > function that zeroizes or wipes memory is subject to removal during > optimization. I often have to look at program's disassembly to ensure > the memset is not removed by the optimizer. > Appropriate use of `volatile`

...ownership to function under darwin9.5.8 and darwin10? The messages discussing this issue are archived at... http://sourceware.org/ml/gdb/2009-09/msg00239.html http://sourceware.org/ml/gdb/2009-09/msg00240.html http://sourceware.org/ml/gdb/2009-09/msg00241.html http://sourceware.org/ml/gdb/2009-09/msg00242.html http://sourceware.org/ml/gdb/2009-09/msg00243.html http://sourceware.org/ml/gdb/2009-09/msg00245.html http://sourceware.org/ml/gdb/2009-09/msg00246.html http://sourceware.org/ml/gdb/2009-09/msg00247.html http://sourceware.org/ml/gdb/2009-09/msg00248.html http://sourceware.org/ml/gdb/2009-09/ms...