newlib-cygwin/newlib/libm/machine/mips/Makefile.am

## Process this file with automake to generate Makefile.in

AM_CPPFLAGS = -I $(abs_newlib_basedir)/libm/common $(NEWLIB_CFLAGS) \
	$(CROSS_CFLAGS) $(TARGET_CFLAGS)

LIB_SOURCES = \
	feclearexcept.c fegetenv.c fegetexceptflag.c \
	fegetround.c feholdexcept.c feraiseexcept.c fesetenv.c \
	fesetexceptflag.c fesetround.c fetestexcept.c feupdateenv.c

noinst_LIBRARIES = lib.a
lib_a_SOURCES = $(LIB_SOURCES)
lib_a_CFLAGS = $(AM_CFLAGS)

LIBADD_OBJS = \
	lib_a-fenv.$(OBJEXT)

# fenv.c cannot be compiled as mips16 since it uses the cfc1 instruction
lib_a-fenv.o: fenv.c
	$(COMPILE) -mno-mips16 -c -o $@ `test -f 'fenv.c' || echo '$(srcdir)/'`fenv.c

lib_a-fenv.obj: fenv.c
	$(COMPILE) -mno-mips16 -c -o $@ `if test -f 'fenv.c'; then $(CYGPATH_W) 'fenv.c'; else $(CYGPATH_W) '$(srcdir)/fenv.c'; fi`
mips fenv support Signed-off-by: Eshan dhawan <eshandhawan51@gmail.com> 2020-07-03 02:43:06 +05:30			`## Process this file with automake to generate Makefile.in`

newlib: use abs_newlib_basedir for -I paths When we had configure scripts in subdirs, the newlib_basedir value was computed relative to that, and it'd be the same when used in the Makefile in the same dir. With many subdir configure scripts removed, the top-level configure & Makefile can't use the same relative path. So switch the subdir Makefiles over to abs_newlib_basedir when they use -I to find source headers. Do this for all subdirs, even ones with configure scripts and where newlib_basedir works. This makes the code consistent, and avoids surprises if the configure script is ever removed in the future as part of merging to the higher level. Some of the subdirs were using -I$(newlib_basedir)/../newlib/ for some reason. Collapse those too since newlib_basedir points to the newlib source tree already. 2022-01-27 19:24:16 -05:00			`AM_CPPFLAGS = -I $(abs_newlib_basedir)/libm/common $(NEWLIB_CFLAGS) \`
mips fenv support Signed-off-by: Eshan dhawan <eshandhawan51@gmail.com> 2020-07-03 02:43:06 +05:30			`$(CROSS_CFLAGS) $(TARGET_CFLAGS)`

			`LIB_SOURCES = \`
			`feclearexcept.c fegetenv.c fegetexceptflag.c \`
			`fegetround.c feholdexcept.c feraiseexcept.c fesetenv.c \`
Modifying patch from: marian.buschsieweke@ovgu.de The code accessing the floating point control/status register, namely #define __cfc1(__fcsr) __asm __volatile("cfc1 %0, $31" : "=r" (__fcsr) does not compile with mips16. This changed the makefile to pass -mno-mips16 to avoid the following compiler error: mips-mti-elf fails with "Error: unrecognized opcode `cfc1 $3,$31'" 2021-11-29 17:33:52 -05:00			`fesetexceptflag.c fesetround.c fetestexcept.c feupdateenv.c`
mips fenv support Signed-off-by: Eshan dhawan <eshandhawan51@gmail.com> 2020-07-03 02:43:06 +05:30
			`noinst_LIBRARIES = lib.a`
			`lib_a_SOURCES = $(LIB_SOURCES)`
			`lib_a_CFLAGS = $(AM_CFLAGS)`

Modifying patch from: marian.buschsieweke@ovgu.de The code accessing the floating point control/status register, namely #define __cfc1(__fcsr) __asm __volatile("cfc1 %0, $31" : "=r" (__fcsr) does not compile with mips16. This changed the makefile to pass -mno-mips16 to avoid the following compiler error: mips-mti-elf fails with "Error: unrecognized opcode `cfc1 $3,$31'" 2021-11-29 17:33:52 -05:00			`LIBADD_OBJS = \`
			`lib_a-fenv.$(OBJEXT)`

			`# fenv.c cannot be compiled as mips16 since it uses the cfc1 instruction`
			`lib_a-fenv.o: fenv.c`
			$(COMPILE) -mno-mips16 -c -o $@ `test -f 'fenv.c' \|\| echo '$(srcdir)/'`fenv.c

			`lib_a-fenv.obj: fenv.c`
			$(COMPILE) -mno-mips16 -c -o $@ `if test -f 'fenv.c'; then $(CYGPATH_W) 'fenv.c'; else $(CYGPATH_W) '$(srcdir)/fenv.c'; fi`