https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78385
Bug ID: 78385
Summary: Build of libgcc2 for target arm-eabi fails, if
configuration --with-abi=apcs-gnu is used (in
GCC-Build)
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: [email protected]
Target Milestone: ---
If I build a Cross-GCC (on/with i686-w64-mingw32 fromm msys2) for
--target=arm-eabi and use additionally the option --with-abi=apcs-gnu (to
compile to OABI as default), the build of libgcc2 (a nearby last phase) will
fail with:
/x/GCC5/.temp/gcc/./gcc/xgcc -B/x/GCC5/.temp/gcc/./gcc/
-B/x/GCC5/V5.X.0/arm-eabi/bin/ -B/x/GCC5/V5.X.0/arm-eabi/lib/ -isystem
/x/GCC5/V5.X.0/arm-eabi/include -isystem /x/GCC5/V5.X.0/arm-eabi/sys-include
-Os @X:/GCC5/.temp/arm-eabi.opt -O2 -Os @X:/GCC5/.temp/arm-eabi.opt -DIN_GCC
-DCROSS_DIRECTORY_STRUCTURE -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -Dinhibit_libc -fno-inline -I. -I. -I../.././gcc
-I../../../../src/gcc-5.X.0/libgcc -I../../../../src/gcc-5.X.0/libgcc/.
-I../../../../src/gcc-5.X.0/libgcc/../gcc
-I../../../../src/gcc-5.X.0/libgcc/../include -o _fixsfdi.o -MT _fixsfdi.o
-MD -MP -MF _fixsfdi.dep -DL_fixsfdi -c
../../../../src/gcc-5.X.0/libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
In file included from ../../../../src/gcc-5.X.0/libgcc/libgcc2.c:56:0:
../../../../src/gcc-5.X.0/libgcc/libgcc2.c: In function '__fixsfdi':
x:\gcc5\src\gcc-5.x.0\libgcc\libgcc2.h:209:20: sorry, unimplemented: PCS
variant
#define __NDW(a,b) __ ## a ## di ## b
^
x:\gcc5\src\gcc-5.x.0\libgcc\libgcc2.h:282:19: note: in expansion of macro
'__NDW'
#define __fixsfdi __NDW(fixsf,)
^~~~~
../../../../src/gcc-5.X.0/libgcc/libgcc2.c:1497:1: note: in expansion of macro
'__fixsfdi'
__fixsfdi (SFtype a)
^~~~~~~~~
make[2]: *** [Makefile:467: _fixsfdi.o] Error 1
Configuration of the previously build Cross-GCC:
>arm-eabi-gcc -v
Using built-in specs.
COLLECT_GCC=\GCC5\V5.X.0\bin\arm-eabi-gcc
COLLECT_LTO_WRAPPER=x:/gcc5/v5.x.0/bin/../libexec/gcc/arm-eabi/6.2.0/lto-wrapper.exe
Target: arm-eabi
Configured with: ../../src/gcc-5.X.0/configure --prefix=/x/GCC5/V5.X.0
--build=i686-w64-mingw32 --target=arm-eabi --disable-nls --disable-shared
--disable-multilib --disable-threads --with-pkgversion='Built by ME, rev.
20161114' --enable-languages=c,c++ --with-gnu-as --with-gnu-ld
--disable-win32-registry --with-arch=armv7-a --with-abi=apcs-gnu
--with-float=softfp --with-fpu=vfpv3 --disable-tls --with-stabs
--disable-__cxa_atexit --disable-decimal-float --disable-libgomp
--disable-libquadmath --disable-libstdcxx-verbose --with-newlib
--with-headers=../../src/newlib-2.3.0/newlib/libc/include
--with-gxx-include-dir=/x/GCC5/V5.X.0/include/c++/5.X.0
--disable-libstdcxx-visibility --enable-fully-dynamic-string
--with-gmp=C:/msys32/mingw32 --with-mpfr=C:/msys32/mingw32
--with-mpc=C:/msys32/mingw32
Thread model: single
gcc version 6.2.0 (Built by ME, rev. 20161114)
Additional information:
Same failure occurs, If I build an GCC 5.4.0 (an same configuration).
IMHO - It seems, that the -mabi-Option apcs-gnu (default) causes this issue on
building of the function '__fixsfdi'; But no fail on e.g. __fixunsdfsi ...
Best regards from Austria,
Markus
