This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/11751] wrong evaluation order of an expression
- From: "nobs at tigress dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 11 Mar 2006 16:10:49 -0000
- Subject: [Bug c/11751] wrong evaluation order of an expression
- References: <bug-11751-6637@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #61 from nobs at tigress dot com 2006-03-11 16:10 -------
referring to duplicate 26642:
The behavior changed between gcc3 and gcc4 and the comment is "there is no
reason the result should not change"?
Sorry, but I think that's a really bad way to handle things. When a update
changes behavior, there should be et least an appropriate warning.
And another comment says "look at the warning you got". If you'd read the
warnings you would have seen it refers to that part of the code that didn't
change its behavior. So a code that only uses the array-version (that behaves
differently) wouldn't get the warning.
I really doubt that there is any good reason that simple variables and array
variables should differ in the order their expressions are solved.
Please, think about it. At least give a warning at the right place!
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11751