This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/26292] Bad code in unsigned shifts
- From: "igodard at pacbell dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 14 Feb 2006 22:18:08 -0000
- Subject: [Bug c++/26292] Bad code in unsigned shifts
- References: <bug-26292-6594@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #4 from igodard at pacbell dot net 2006-02-14 22:18 -------
"undefined" takes care of the 4.0.2 case, and the first part of the Cygwin
case. But the shift that produces "d" in the Cygwin case has a right operand of
zero and a left operand (what the undefined gave as "c") also zero, but it
produces "7fffffff". Or does an undefined propagate outward through
parentheses, so that the result of any expression one of whose components
(however deeply nested) is undefined is also undefined? Is "true ||
(<undefined>)" also undefined? If so then neither of my cases is a bug, but if
not then there's a problem on Cygwin 3.4.4.
Ivan
--
igodard at pacbell dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26292