Re: [avr-gcc-list] Byte values promted to int when during compare

[hanzl]

>>> unsigned char A,B; ... A & 15 != B ...

>>  It seems that A is promoted to int before the binary & operation ?
>>  But why?
>
> Because the C standard says so.

And because the compiler was not clever enough (or was not instructed
to do so?) to optimize this back to byte-only operations?

It seems to me that in many practical cases (like the one above) we
can have both strict ISO and quick code through clever enough
optimization.

Or maybe we already have it? Somebody knows?

Regards

Vaclav Hanzl