Attached to Project: CRUX-ARM
Opened by Victor Martinez - 2013-09-11
Last edited by Victor Martinez - 2013-09-20
Opened by Victor Martinez - 2013-09-11
Last edited by Victor Martinez - 2013-09-20
FS#54 - gcc: clfs/usr/lib/libitm.a is built for armv4
We find this on current toolchain:
clfs/usr/lib/libitm.a(sjlj.o)
Attribute Section: aeabi
File Attributes
Tag_CPU_arch: v4
while it should be:
Tag_CPU_arch: v5T
Building without specifying –disable-sjlj enables this support by default
From http://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html –enable-sjlj-exceptions
Forces old, set-jump/long-jump exception handling model. If at all possible, the new, frame unwinding exception handling routines should be used instead, as they significantly reduce both runtime memory usage and executable size. This option can change the library ABI.
After rebuilding the toolchain with –disable-sjlj in gcc-static/final clfs/usr/lib/libitm.a isn’t built.
Closed by Victor Martinez
Friday, 20 September 2013, 16:29 GMT
Reason for closing: Not a bug
Additional comments about closing:
Friday, 20 September 2013, 16:29 GMT
Reason for closing: Not a bug
Additional comments about closing:
See comments
After toolchain rebuild without all unneeded options (–with-arch= and –with-fpu) in both stages, static and final, the lib libitm.a isn’t built.
Rebuilding again crossrootfs/gcc with this last toolchain created, this behaviour persists.
libitm.a contains sjlj.o built for armv4
It’s an expected behaviour. See the comment in http://gcc.gnu.org/ml/gcc/2013-09/msg00185.html