------- Comment #1 from jakub at gcc dot gnu dot org 2009-02-03 10:06 -------
Similarly
__typeof (0r)
foo (void)
{
return 0r;
}
ICEs on x86-64 and so does
_Fract foo (void)
{
return 0r;
}
(the last one just as error-recovery ICE). I'd say for
!targetm.fixed_point_supported_p () we should remove the loop hole that
fixed-point constants introduce fixed point types without any error, similarly
for C++ we should reject FIXED_CSTs, and to improve error-recovery, we
shouldn't used fixed point types after we've diagnosed we don't support them.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org
|dot org |
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2009-02-03 10:06:51
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39059
