The following bug occurs only if -O (or higher optimization) is switched on. I did not find out which of the single optimization switches is responsible for it. The complete if statement is true, although none of each boolean value is true. If I replace the enum variable "Type" by an int, the code works correct even with optimization. Please let me know if this bug is already known or even fixed. Compiler: ../configure --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld --disable-nls Thread model: posix gcc version 3.4.1 System (uname -a) SunOS sun2 5.9 Generic_112233-12 sun4u sparc SUNW,Sun-Blade-1500 //gcc -O enumtest.cpp (has the bug) //gcc -O enumtest.cpp -lsupc++ (has the bug) //or: gcc enumtest.cpp -lsupc++ (is correct) //output is(if used -O ): //>inside //>done //output is(if not used -O ): //>done //(as I expect) #include <stdio.h> enum ETestType { e_Zero = 0 , e_One , e_Two , e_Three , e_Four }; int main () { ETestType Type= e_Four; if( ( Type == e_One ) || ( Type == e_Two ) || ( Type == e_Three ) ) { printf("inside\n"); } printf("done\n"); return 0; } David
This is a dup of bug 16372 which was fixed in 3.4.2. *** This bug has been marked as a duplicate of 16372 ***