http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> --- (In reply to Daniel Oertwig from comment #5) > (In reply to Andrew Pinski from comment #3) > > taskInfo.ready[priority]->wakeTime = Task_enforceTimeslice(priority); > > > > This is the same as: > > (*taskInfo.ready[priority]).wakeTime = Task_enforceTimeslice(priority); > > > > Which means either the compiler can read the value of > > taskInfo.ready[priority] before or after the function call to > > Task_enforceTimeslice because there is no sequence point between them. > > Shouldn't the compiler recognize that enforceTimeslice is altering the > global variable? No because without sequence point the left hand side or right hand side can be done first.