http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59990
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > If it is ok that thiscase aborts and the #c0 should not, then the bug would > be in fold-const.c and we should use integral types instead of floating > point types to fold the copy. If this testcase shouldn't abort too, then it > is a target issue, where it should avoid the i387 loads if the result isn't > used in some arithmetic instruction. I disagree, using FP types to implement memcpy in the middle-end is a no-no, i387 isn't the only architecture which can fiddle with FP values.
