------- Comment #63 from dberlin at gcc dot gnu dot org 2006-03-11 16:49 ------- (In reply to comment #61) > referring to duplicate 26642: > > The behavior changed between gcc3 and gcc4 and the comment is "there is no > reason the result should not change"?
There is simply no guarantee at all that the behavior of this will or won't change. It's undefined code. It could change depending on the phase of the moon. > > 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. Unfortunately, it is impossible to warn for every permuation of undefined code at compilation time. However, in general, if you write code whose semantics are undefined, you are going to get burned. This is just the way the ball bounces. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11751
