Back to bug 16693

Who When What Removed Added
p.r.gotch 2004-07-23 17:20:29 UTC Known to fail 3.4.0 3.4.1
Known to work 3.3.3 3.5.0
Summary Bitwise AND is lost when used within a cast to an enum of the same precision Bitwise AND is lost when used within a cast to an enum of the same precision
pinskia 2004-07-23 17:22:52 UTC Keywords wrong-code
Summary Bitwise AND is lost when used within a cast to an enum of the same precision [3.4 Regression] Bitwise AND is lost when used within a cast to an enum of the same precision
Target Milestone --- 3.4.2
bangerth 2004-07-23 19:04:45 UTC Status UNCONFIRMED NEW
Ever confirmed 1
Last reconfirmed 0000-00-00 00:00:00 2004-07-23 19:04:45
Summary [3.4 Regression] Bitwise AND is lost when used within a cast to an enum of the same precision [3.4/3.5 regression] Bitwise AND is lost when used within a cast to an enum of the same precision
bangerth 2004-07-23 19:06:13 UTC Known to fail 3.4.0 3.4.1 3.4.0 3.4.1 3.5.0
Known to work 3.3.3 3.5.0 3.3.3
p.r.gotch 2004-07-24 00:15:00 UTC Target i686-pc-linux-gnu
p.r.gotch 2004-07-26 13:02:59 UTC Known to work 3.3.3 3.3.3 3.3.4
pinskia 2004-08-10 01:25:07 UTC Severity normal critical
reichelt 2004-08-10 09:05:11 UTC Keywords monitored
CC reichelt
pinskia 2004-08-11 16:24:01 UTC Component c++ middle-end
mmitchel 2004-08-19 21:31:03 UTC Status NEW RESOLVED
Resolution --- INVALID
rearnsha 2004-08-20 09:33:30 UTC CC mmitchel
Status RESOLVED REOPENED
Resolution INVALID ---
mmitchel 2004-08-22 23:30:45 UTC CC roger
Assignee unassigned roger
Status REOPENED ASSIGNED
pinskia 2004-08-25 17:28:19 UTC Known to work 3.3.3 3.3.4 3.3.3 3.3.4 3.4.2
Summary [3.4/3.5 regression] Bitwise AND is lost when used within a cast to an enum of the same precision [3.5 regression] Bitwise AND is lost when used within a cast to an enum of the same precision
Target Milestone 3.4.2 3.5.0
pinskia 2004-08-25 20:58:57 UTC Status ASSIGNED RESOLVED
Resolution --- FIXED
rearnsha 2004-08-26 12:33:27 UTC Known to work 3.3.3 3.3.4 3.4.2 3.3.3 3.3.4 3.4.2 3.5.0
Target Milestone 3.5.0 3.4.2
Known to fail 3.4.0 3.4.1 3.5.0 3.4.0 3.4.1

Back to bug 16693