Hello,
Since the -mieee behavior has been fixed, is enabled by default on SH
and the additional flags in libgcc can be removed.
OK?
Cheers,
Oleg
libgcc/ChangeLog:
PR target/33135
* config/sh/t-sh (HOST_LIBGCC2_CFLAGS): Delete.
* config/sh/t-netbsd (HOST_LIBGCC2_CFLAGS): Delete.
* config/sh/t-linux (HOST_LIBGCC2_CFLAGS): Remove mieee option.
Index: libgcc/config/sh/t-sh
===================================================================
--- libgcc/config/sh/t-sh (revision 192050)
+++ libgcc/config/sh/t-sh (working copy)
@@ -59,5 +59,3 @@
libgcc-4-300.a: div_table-4-300.o
$(AR_CREATE_FOR_TARGET) $@ div_table-4-300.o
-HOST_LIBGCC2_CFLAGS += -mieee
-
Index: libgcc/config/sh/t-netbsd
===================================================================
--- libgcc/config/sh/t-netbsd (revision 192050)
+++ libgcc/config/sh/t-netbsd (working copy)
@@ -1,3 +1,2 @@
LIB1ASMFUNCS_CACHE = _ic_invalidate
-HOST_LIBGCC2_CFLAGS += -mieee
Index: libgcc/config/sh/t-linux
===================================================================
--- libgcc/config/sh/t-linux (revision 192051)
+++ libgcc/config/sh/t-linux (working copy)
@@ -2,7 +2,7 @@
LIB2ADD = $(srcdir)/config/sh/linux-atomic.c
-HOST_LIBGCC2_CFLAGS += -mieee -DNO_FPSCR_VALUES
+HOST_LIBGCC2_CFLAGS += -DNO_FPSCR_VALUES
# Silence atomic built-in related warnings in linux-atomic.c.
# Unfortunately the conflicting types warning can't be disabled selectively.
