This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/17507] Problems with shift and increment operator precedence
- From: "work at paul dot dubuc dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 15 Sep 2004 20:32:40 -0000
- Subject: [Bug c++/17507] Problems with shift and increment operator precedence
- References: <20040915184232.17507.work@paul.dubuc.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From work at paul dot dubuc dot org 2004-09-15 20:32 -------
(In reply to comment #7)
> (In reply to comment #6)
> > As for question 1) The standard says that the result is undefined, i.e.
> > the compiler can do whatever it pleases. That includes doing one of
> > the increments, four in the same order in which the appear left to
> > right, four in the reverse order, etc. It isn't a bug, but an opportunity
> > the standard leaves to the compiler writers to implement optimizations.
>
> Regardless of the order that the increment is done in this statement, I would
> expect it to be done 4 times (not only once) by the time the statement ends.
To be very clear here I should have said "incremented by 4, not just by 1".
Sorry.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17507