This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/20531] gcc should warn about undefined behaviour
- From: "jsm28 at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 19 Mar 2005 13:18:05 -0000
- Subject: [Bug c/20531] gcc should warn about undefined behaviour
- References: <20050318104612.20531.pluto@pld-linux.org>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From jsm28 at gcc dot gnu dot org 2005-03-19 13:18 -------
I see no undefined behavior here. The order is unspecified, not undefined,
and there is nothing more wrong with accessing two volatile objects between
sequence points than there would be in (s.x = 1) + (s.y = 2) modifying
both objects (volatile or not) without an intervening sequence point.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20531