Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/arm: add support for thumb(1) mode
Date: Wed, 17 Jul 2013 13:03:56 -0300	[thread overview]
Message-ID: <51E6C06C.8070300@zacarias.com.ar> (raw)
In-Reply-To: <20130717175838.2fc2831e@skate>

On 07/17/2013 12:58 PM, Thomas Petazzoni wrote:

> I think this is misleading: Thumb doesn't allow to mix 16 bits and 32
> bits instructions like Thumb2 does. IIRC, with Thumb, a particular
> function needs to be either completely Thumb (16 bits) or completely
> ARM (32 bits), and there is the thumb-interworking mechanism between
> the two.
> 
> Which leads me to this question: is adding Thumb support as simple as
> what you're adding? Aren't there some additional thumb-interworking
> complexities to handle?

http://infocenter.arm.com/help/topic/com.arm.doc.ihi0042e/IHI0042E_aapcs.pdf
Section 5.6 is of interest, once OABI (APCS) was dropped interworking
isn't that hard since it's mandatory for AAPCS.
Regards.

  reply	other threads:[~2013-07-17 16:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 15:39 [Buildroot] [PATCH] arch/arm: add support for thumb(1) mode Gustavo Zacarias
2013-07-17 15:58 ` Thomas Petazzoni
2013-07-17 16:03   ` Gustavo Zacarias [this message]
2013-07-17 19:58     ` Thomas Petazzoni
2013-07-17 22:25       ` Gustavo Zacarias
2013-07-18  7:19         ` Thomas Petazzoni
2013-07-18 11:08           ` Gustavo Zacarias
2013-07-18 11:24             ` Thomas Petazzoni
2013-07-18  8:10         ` Peter Korsgaard
2013-07-18 16:07           ` Gustavo Zacarias
2013-07-18 22:32             ` Peter Korsgaard
2013-07-18 22:46               ` Gustavo Zacarias
2013-07-19  8:19                 ` Peter Korsgaard
2013-07-19 13:06                   ` Gustavo Zacarias
2013-07-17 22:22 ` Peter Korsgaard

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=51E6C06C.8070300@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --cc=buildroot@busybox.net \
    /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