This is the mail archive of the libffi-discuss@sourceware.org mailing list for the libffi project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Questions about the libffi development process


On 04/23/2015 03:49 PM, Russell Keith-Magee wrote:
> None at all? There's no release candidate process? No release testing
> procedures?

I Anthony will have to answer that.

> libtool: compile:  xcrun -sdk iphoneos clang -arch armv7
> -DHAVE_CONFIG_H -I. -I.. -I. -I../include -Iinclude -I../src -I.
> -I../include -Iinclude -I../src -miphoneos-version-min=7.0 -MT
> src/arm/sysv.lo -MD -MP -MF src/arm/.deps/sysv.Tpo -c
> ../src/arm/sysv.S  -fno-common -DPIC -o src/arm/.libs/sysv.o
> ../src/arm/sysv.S:111:2: error: .arch directive not valid for Mach-O
>  .arch armv5t

Any chance you know what is the base architecture for iOS on ARM?

> ../src/arm/sysv.S:128:8: error: invalid operand for instruction
>  ldcle p11, cr0, [r0] @ vldrle d0, [sp]
>        ^

Try replacing these with the comment (text after @) and see if it assembles.

The generic "coprocessor load" instructions are used instead of the more
specific vfp load instructions in order to support armv7hf at run-time while
not requiring more than arm5t at compile-time.  Something that makes sense for
ELF, but I guess not for iOS.


r~


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]