[Bug c/32531] New: erroneous enum comparison results

2007-06-27 Thread entrophage at gmail dot com
mmary: erroneous enum comparison results Product: gcc Version: 4.1.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: entrophage at gmail dot com

[Bug c/32531] erroneous enum comparison results

2007-06-27 Thread entrophage at gmail dot com
--- 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 fo

[Bug c/32531] erroneous enum comparison results

2007-06-27 Thread entrophage at gmail dot com
--- 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 -Wextr

[Bug c/32531] erroneous enum comparison results

2007-06-27 Thread entrophage at gmail dot com
--- 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 L

[Bug c/32531] erroneous enum comparison results

2007-06-27 Thread entrophage at gmail dot com
--- 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 m