------- Additional Comments From schlie at comcast dot net 2004-10-19 21:18 ------- Subject: Re: wrong built-in functions selected
Nope, please look at the coded examples: - they demonstrate that: (signed char) % (signed char) => invokes (int) % (int), not correct. - and the compiler consistently treats rhs immediate value differently than lhs immediate values for some non-descript reason? (arguably, it should assume all immediate values are ints unless cast/specified otherwise, but that's not what it does, nor does it properly treat lhs operands as signed chars even if properly explicitly cast. Thanks, -paul- > From: pinskia at gcc dot gnu dot org <[EMAIL PROTECTED]> > Reply-To: <[EMAIL PROTECTED]> > Date: 19 Oct 2004 20:39:44 -0000 > To: <[EMAIL PROTECTED]> > Subject: [Bug target/18065] wrong built-in functions selected > > > ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-19 > 20:39 ------- > char ss = s % s ; //<__divmodhi4> wrong, should be 8-bit <__divmodqi4> > This is not wrong as we sign extend the arguments as required by the C > standard (to int). > > So this is just an missed-optimization. > > -- > What |Removed |Added > ---------------------------------------------------------------------------- > Severity|critical |minor > Component|c |target > Keywords| |missed-optimization > > > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18065 > > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18065
