From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] dmalloc: Force arm mode instead of Thumb1 mode
Date: Mon, 26 Jan 2015 12:20:04 +0100 [thread overview]
Message-ID: <20150126122004.35d069a7@free-electrons.com> (raw)
In-Reply-To: <CACQ1gAj44T_KaGN3ZToxjiQGj3P_ghJwbjxxRRWTA2jAqVR9bA@mail.gmail.com>
Dear Richard Genoud,
On Mon, 26 Jan 2015 12:07:42 +0100, Richard Genoud wrote:
> > Are you actually using an ARMv4/ARMv5 Thumb system?
> I tried to use it to know if it saves some place on my RFS, but as Qt
> has the same kind of problem with Thumb1, it didn't make a big
> difference.
> (my platform is a sam9g35, so ARMv5)
> But if I continue to have spaces problem, I will reconsider using
> thumb1, and maybe try to patch the Qt assembly to make it Thumb1
> compliant instead of adding " -marm"
Ok.
> > Maybe this is a configuration we should add to our autobuilders, since
> > it's currently not even build-tested.
> That may be a good idea since I may not be the only potential user :)
Indeed. We also have more autobuilder instances nowadays, so adding a
few more configurations should be fine.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-26 11:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 11:24 [Buildroot] [PATCH 1/3] dmalloc: Force arm mode instead of Thumb1 mode Richard Genoud
2015-01-20 11:24 ` [Buildroot] [PATCH 2/3] alsa-lib: " Richard Genoud
2015-02-02 17:20 ` Arnout Vandecappelle
2015-02-02 17:29 ` Peter Korsgaard
2015-02-02 17:32 ` Arnout Vandecappelle
2015-01-20 11:24 ` [Buildroot] [PATCH 3/3] qt: " Richard Genoud
2015-02-02 17:35 ` Arnout Vandecappelle
2015-02-02 20:42 ` Peter Korsgaard
2015-01-25 19:31 ` [Buildroot] [PATCH 1/3] dmalloc: " Thomas Petazzoni
2015-01-26 11:07 ` Richard Genoud
2015-01-26 11:20 ` Thomas Petazzoni [this message]
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=20150126122004.35d069a7@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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.