Re: [avr-gcc-list] avr-g++ local variable constructor / block body / destructor execution order

2007-09-06 Thread David Brown
Oleksandr Redchuk wrote: 2007/9/2, David Brown [EMAIL PROTECTED]: Similarly, if you have multiple objects being constructed or destructed, their ordering is *not* guaranteed by the compiler AFAIR, this order guaranteed for objects in block of code and for objects in file - in order of

Re: [avr-gcc-list] avr-g++ local variable constructor / block body/ destructor execution order

2007-09-06 Thread Graham Davies
David Brown wrote: I believe [the compiler] can [change order of ... volatile objects access]. Obviously it is only legal if such moves do not affect the volatile accesses themselves. Perhaps someone here who has a better knowledge of the standards ... I wouldn't claim better knowledge, but

Re: [avr-gcc-list] avr-g++ local variable constructor / block body/destructor ex

2007-09-06 Thread Dave Hansen
From: Graham Davies [EMAIL PROTECTED] David Brown wrote: I believe [the compiler] can [change order of ... volatile objects access]. Obviously it is only legal if such moves do not affect the volatile accesses themselves. Perhaps someone here who has a better knowledge of the standards