http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53013

--- Comment #2 from john.stevens at f5 dot com 2012-04-16 21:47:11 UTC ---
I would respectfully point out that "consistent", and "undefined by the
standard", are two different things.

I can expect consistent behavior that is not defined by the standard, but I
agree that I may not expect that that behavior will be defined by the standard,
nor that it will remain the same from one version to the next, only that the
result generated by the same operation will give the same,
undefined-by-the-standard, but consistent result.

IOW, "undefined" means the standard deliberately refuses to make a statement
about a real thing, it does not mean that the thing is not real.  The
difference here is akin to the difference between Philosophy and Natural
Philosophy (Natural Philosophy being a proper subset of Philosophy that
deliberately refrains from discussing real things that are outside the realm of
Natural Philosophy).

Thanks,
John S.

-----Original Message-----
From: manu at gcc dot gnu.org [mailto:gcc-bugzi...@gcc.gnu.org] 
Sent: Monday, April 16, 2012 2:17 PM
To: John Stevens
Subject: [Bug c/53013] Inconsistent Behaviour with Left Shift Operator.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53013

Manuel López-Ibáñez <manu at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |manu at gcc dot gnu.org
         Resolution|                            |INVALID

--- Comment #1 from Manuel López-Ibáñez <manu at gcc dot gnu.org> 2012-04-16
21:16:48 UTC --- Sorry, you cannot expect consistency from undefined behaviour.
It doesn't work that way: http://c-faq.com/ansi/undef.html

And if you want to know why:
http://www.eskimo.com/~scs/readings/undef.950321.html

--
Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: ------- You reported the bug.

Reply via email to