------- Comment #7 from pinskia at gcc dot gnu dot org 2005-10-25 19:22 ------- (In reply to comment #6) > - For some reason, GCC is casting "char" to "int" prior to returning their > value as a "char", which > although works, is a fairly gross mis-optimization? (which should also > likely be considred a bug).
That is an ABI issue. Also it is most likely not able to change as some people
still use K&R C where
f()
{
return 1;
}
Is still valid.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20937
