------- Comment #2 from pinskia at gcc dot gnu dot org 2008-07-02 22:44 ------- The use of "o" is most likely wrong here and most likely not a GCC issue as you are saying you access the memory when in reality you don't.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36706
