--- Comment #5 from pinskia at gcc dot gnu dot org 2007-06-28 02:04 ---
No, the comparision is correct.
The enum is you gave is equalivant (in both C and C++) to:
enum X
{
A = 3,
B = 1,
C = 2,
D = 3,
E = 4
};
--
pinskia at gcc dot gnu dot org changed:
--- Comment #4 from entrophage at gmail dot com 2007-06-28 01:58 ---
(In reply to comment #3)
> valgrind of the resulting binary shows interesting output:
this is irrelevant since binary compiled from the following trivial source file
gives the same valgrind errors.
int main()
{
re
--- Comment #3 from entrophage at gmail dot com 2007-06-28 01:53 ---
valgrind of the resulting binary shows interesting output:
$ valgrind ./foo
==5107== Memcheck, a memory error detector.
==5107== Copyright (C) 2002-2007, and GNU GPL'd, by Julian Seward et al.
==5107== Using LibVEX rev
--- Comment #2 from entrophage at gmail dot com 2007-06-28 01:50 ---
Created an attachment (id=13800)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13800&action=view)
preprocessor output of the source file that reproduces the bug
generated with:
$ gcc -Wall -Wextra -ansi -pedantic
--- Comment #1 from entrophage at gmail dot com 2007-06-28 01:49 ---
Created an attachment (id=13799)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13799&action=view)
source file to reproduce the bug
compile with:
$ gcc -Wall -Wextra -ansi -pedantic -save-temps -o foo foo.c
--
