Slackware - ARM This forum is for the discussion of Slackware ARM. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
04-02-2015, 03:02 PM
|
#1
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Rep:
|
gcc bootstrap fails with --with-fpu=neon-vfpv4
configuration parameters include:
Code:
--with-cpu=cortex-a7 --with-tune=cortex-a7 --with-arch=armv7-a --with-float=softfp --with-fpu=neon-vfpv4 --disable-werror
and produces:
Code:
/bin/sh ./libtool --tag=CC --mode=compile /home/woland/tmp/build-gcc/gcc.build.lnx/./gcc/xgcc -B/home/woland/tmp/build-gcc/gcc.build.lnx/./gcc/ -B/usr/arm-slackware-linux-gnueabi/bin/ -B/usr/arm-slackware-linux-gnueabi/lib/ -isystem /usr/arm-slackware-linux-gnueabi/include -isystem /usr/arm-slackware-linux-gnueabi/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc-4.8.4/libgo -I ../../../gcc-4.8.4/libgo/runtime -I../../../gcc-4.8.4/libgo/../libffi/include -I../libffi/include -pthread -fexceptions -fplan9-extensions -Wall -Wextra -Wwrite-strings -Wcast-qual -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I ../../../gcc-4.8.4/libgo/../libgcc -I ../../../gcc-4.8.4/libgo/../libbacktrace -I ../../gcc/include -g -O2 -march=armv7-a -mtune=cortex-a7 -mfloat-abi=softfp -MT go-type-complex.lo -MD -MP -MF .deps/go-type-complex.Tpo -c -o go-type-complex.lo `test -f 'runtime/go-type-complex.c' || echo '../../../gcc-4.8.4/libgo/'`runtime/go-type-complex.c
libtool: compile: /home/woland/tmp/build-gcc/gcc.build.lnx/./gcc/xgcc -B/home/woland/tmp/build-gcc/gcc.build.lnx/./gcc/ -B/usr/arm-slackware-linux-gnueabi/bin/ -B/usr/arm-slackware-linux-gnueabi/lib/ -isystem /usr/arm-slackware-linux-gnueabi/include -isystem /usr/arm-slackware-linux-gnueabi/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc-4.8.4/libgo -I ../../../gcc-4.8.4/libgo/runtime -I../../../gcc-4.8.4/libgo/../libffi/include -I../libffi/include -pthread -fexceptions -fplan9-extensions -Wall -Wextra -Wwrite-strings -Wcast-qual -D_GNU_SOURCE -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I ../../../gcc-4.8.4/libgo/../libgcc -I ../../../gcc-4.8.4/libgo/../libbacktrace -I ../../gcc/include -g -O2 -march=armv7-a -mtune=cortex-a7 -mfloat-abi=softfp -MT go-type-complex.lo -MD -MP -MF .deps/go-type-complex.Tpo -c ../../../gcc-4.8.4/libgo/runtime/go-type-complex.c -fPIC -DPIC -o .libs/go-type-complex.o
../../../gcc-4.8.4/libgo/runtime/go-type-complex.c: In function '__go_type_hash_complex':
../../../gcc-4.8.4/libgo/runtime/go-type-complex.c:87:1: error: unrecognizable insn:
}
^
(insn 99 98 100 17 (set (reg:DI 175 [ D.9567 ])
(unspec:DI [
(mem/c:DI (plus:SI (reg/f:SI 105 virtual-stack-vars)
(const_int -24 [0xffffffffffffffe8])) [6 S8 A32])
] UNSPEC_MISALIGNED_ACCESS)) ../../../gcc-4.8.4/libgo/runtime/go-type-complex.c:51 -1
(nil))
../../../gcc-4.8.4/libgo/runtime/go-type-complex.c:87:1: internal compiler error: in extract_insn, at recog.c:2154
0x38cb63 _fatal_insn(char const*, rtx_def const*, char const*, int, char const*)
../../gcc-4.8.4/gcc/rtl-error.c:109
0x38cbb7 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
../../gcc-4.8.4/gcc/rtl-error.c:117
0x35f1af extract_insn(rtx_def*)
../../gcc-4.8.4/gcc/recog.c:2154
0x2611e7 instantiate_virtual_regs_in_insn
../../gcc-4.8.4/gcc/function.c:1565
0x2611e7 instantiate_virtual_regs
../../gcc-4.8.4/gcc/function.c:1932
Please submit a full bug report,
For details, see Bug 65664
|
|
|
04-03-2015, 09:07 AM
|
#2
|
Senior Member
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199
Rep: 
|
|
|
|
04-03-2015, 12:18 PM
|
#3
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Original Poster
Rep:
|
Quote:
Originally Posted by Keruskerfuerst
|
It is not clear to me how this link can help in fixing the problem, which seems to be related to how gcc compiles code for the armv7-a/neon combination.
|
|
|
04-03-2015, 12:30 PM
|
#4
|
Senior Member
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199
Rep: 
|
If you have a look at the GNU GCC manual ( https://gcc.gnu.org/onlinedocs/gcc-4.8.4/gcc.pdf), you wont find with-fpu=neon-vfpv4.
|
|
|
04-03-2015, 12:36 PM
|
#5
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Original Poster
Rep:
|
Quote:
Originally Posted by Keruskerfuerst
|
I am afraid you are confusing compiler options with bootstrap parameters.
--with-fpu=neon-vfpv4 makes -mfpu=neon-vfpv4 the default for the compiler: see Installing GCC: Configuration
Quote:
--with-schedule=cpu
--with-arch=cpu
--with-arch-32=cpu
--with-arch-64=cpu
--with-tune=cpu
--with-tune-32=cpu
--with-tune-64=cpu
--with-abi=abi
--with-fpu=type
--with-float=type
These configure options provide default values for the -mschedule=, -march=, -mtune=, -mabi=, and -mfpu= options and for -mhard-float or -msoft-float. As with --with-cpu, which switches will be accepted and acceptable values of the arguments depend on the target.
|
|
|
|
04-04-2015, 08:20 AM
|
#6
|
Senior Member
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199
Rep: 
|
You may try to use the actual version of gcc: https://gcc.gnu.org/mirrors.html
|
|
|
04-04-2015, 08:56 AM
|
#7
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Original Poster
Rep:
|
Quote:
Originally Posted by Keruskerfuerst
|
Can you please elaborate on what you mean by "actual version"?
|
|
|
04-04-2015, 09:06 AM
|
#8
|
Senior Member
Registered: Oct 2005
Location: Horgau, Germany
Distribution: Manjaro KDE, Win 10
Posts: 2,199
Rep: 
|
I have searched through the bug database of gentoo. The error you have posted is not in the bug database.
Actual version: i mean gcc version 4.9.2. Maybe this version works better.
|
|
|
04-04-2015, 09:08 AM
|
#9
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Original Poster
Rep:
|
Quote:
Originally Posted by Keruskerfuerst
I have searched through the bug database of gentoo. The error you have posted is not in the bug database.
Actual version: i mean gcc version 4.9.2. Maybe this version works better.
|
If you have gcc 4.9.2 installed on an arm machine, I will be happy to share with you a small package of source code for testing whether the same error can be reproduced.
|
|
|
04-04-2015, 09:10 AM
|
#10
|
Member
Registered: Oct 2012
Location: Halifax, NS, Canada
Distribution: Slackware
Posts: 34
Original Poster
Rep:
|
Patch that makes the problem disappear
The following patch makes the problem go away insofar as bootstrap is concerned:
http://gcc.gnu.org/ml/gcc-patches/2014-05/msg02510.html
The patch involves rewriting certain functions for libgo.
The aforementioned errors can still be reproduced if one attempts to compile the old libgo files with certain parameters.
|
|
|
All times are GMT -5. The time now is 05:18 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|