From: Tor Krill <tor@openproducts.com>
To: libffi-discuss@sourceware.org
Subject: libffi on Cortex M4?
Date: Mon, 14 Sep 2015 18:43:00 -0000 [thread overview]
Message-ID: <1442256188.3397.27.camel@openproducts.com> (raw)
Dear list,
I'm trying to crosscompile libffi for a Cortex-M4 platform running
uClinux but this fails miserably during compilation with a:
../src/arm/sysv.S: Assembler messages:
../src/arm/sysv.S:152: Error: selected processor does not support ARM
opcodes
../src/arm/sysv.S:154: Error: attempt to use an ARM instruction on a
Thumb-only processor -- `stmfd sp!,{r0-r3,fp,lr}'
../src/arm/sysv.S:156: Error: attempt to use an ARM instruction on a
Thumb-only processor -- `mov fp,sp'
../src/arm/sysv.S:161: Error: attempt to use an ARM instruction on a
Thumb-only processor -- `sub sp,fp,r2'
My question is simply, is thumb2 on a cortex m4 supported by libffi?
I.e. is it my build setup that is faulty and this should work or is this
unsupported?
sysv.S have indications that it should support thumb instructions but it
seems to be ignored when i compile libffi.
Best!
/Tor
next reply other threads:[~2015-09-14 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-14 18:43 Tor Krill [this message]
2015-09-14 19:08 ` Richard Henderson
2015-09-15 11:52 ` Tor Krill
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1442256188.3397.27.camel@openproducts.com \
--to=tor@openproducts.com \
--cc=libffi-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).