--- Comment #5 from gurganbl at rose-hulman dot edu 2006-07-26 11:42
---
That would be a problem in assignment, not in the conditional. Additionally, if
I do unsigned int baz = 0;
signed int bar = -1;
baz = bar;
I get no warning. I agree with what you say about there being a problem
--- Comment #3 from gurganbl at rose-hulman dot edu 2006-07-26 03:43
---
Created an attachment (id=11942)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11942&action=view)
generated assembly
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28488
--- Comment #2 from gurganbl at rose-hulman dot edu 2006-07-26 03:42
---
Created an attachment (id=11941)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11941&action=view)
preprocessesed source
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28488
--- Comment #1 from gurganbl at rose-hulman dot edu 2006-07-26 03:41
---
Created an attachment (id=11940)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=11940&action=view)
original source
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28488
ing says signed and unsigned type in
conditional expression
Product: gcc
Version: 4.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy:
