From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Making thumb builds easier in OE
Date: Sat, 25 Oct 2008 13:35:30 +0200 [thread overview]
Message-ID: <gdv0a2$u5k$1@ger.gmane.org> (raw)
Hi,
I noticed that Phil fixed thumb interworking in glibc for armv4t which
spurred me to do this:
arm tune files: include tune-thumb by default
* it defaults to non-thumb, so no functional change
So people can now set ARM_INSTRUCTION_SET = "thumb" and resulting ARM
builds will be in thumb mode.
This does raise a few issues:
1) How can we handle thumb2? I only changed the arm9 and arm11 tune
files, how should we do the arm1176 and cortex ones?
2) Since thumb packages are compatible with non-thumb ones we don't
really need a seperate arch, but keeping them same feels wrong and is a
QA nightmare.
for 2) my first thought was to add '-thumb' to the archs, like angstrom
adds '-oabi' for strongarm packages.
I'm not really interested in a discussion whether thumb(2) is worth it,
I just want to solve the build- and distro side of it.
Thought suggestions?
regards,
Koen
next reply other threads:[~2008-10-25 11:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-25 11:35 Koen Kooi [this message]
2008-10-26 19:13 ` Making thumb builds easier in OE Phil Blundell
2008-10-26 19:46 ` Koen Kooi
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='gdv0a2$u5k$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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