From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/arm: add support for thumb(1) mode
Date: Fri, 19 Jul 2013 00:32:16 +0200 [thread overview]
Message-ID: <87mwpjwlcf.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <51E812BF.9060808@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 18 Jul 2013 13:07:27 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> On 07/18/2013 05:10 AM, Peter Korsgaard wrote:
>> FYI, I just did a test build (arm926/thumb1/internal uclibc), and the
>> build dies in NPTL when it runs out of registers. Without threads it
>> builds and seems to work.
Gustavo> I regularly build -mthumb (via CFLAGS) projects without issues for an
Gustavo> arm920t, but that doesn't force those flags for uclibc, just catched the
Gustavo> breakage after you fixed my patch (mine was a no-op, d'oh!)
Gustavo> Seems uclibc is broken for thumb builds, even with
Gustavo> COMPILE_IN_THUMB_MODE=y in its config (which the only thing it does is
Gustavo> add -mthumb to the compile flags).
Actually the uClibc breakage seems to only be in the NPTL stuff. A test
build without threads worked OK.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2013-07-18 22:32 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
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 [this message]
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=87mwpjwlcf.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.