Hi Carlos It would be interresting to test wether the same bug happens with lower numbers. Because I found two different reasons for this behaviours : either there's a problem with assigning 128 to a signed char (which is supposed to be bound to -128 +127) or it is caussed by an implicit cast during the comparison.
It's strange because gcc haven't this behaviour. regards, Romain On Jan 6, 2014 4:58 PM, "Carlos Montiers" <[email protected]> wrote: > Hello. Please can add support for tiny c warning signed comparisions with > unsigned comparisions. > > For warning code like this: > > #include <stdio.h> > int main() > { > char num_signed = 128; > unsigned char num_unsigned = 128; > if (num_signed == num_unsigned) { > printf("Equals\n"); > } else { > printf("Not Equals\n"); > } > return 0; > } > > > > _______________________________________________ > Tinycc-devel mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/tinycc-devel > >
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
