All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: Koen Kooi <openembedded-devel@lists.openembedded.org>
Subject: Re: [RFC] Enable tune-thumb.inc for all armv5t and armv6t machines
Date: Thu, 21 Dec 2006 19:44:02 +0200	[thread overview]
Message-ID: <1151969252.20061221194402@gmail.com> (raw)
In-Reply-To: <458AC366.3030405@dominion.kabel.utwente.nl>

Hello Koen,

Thursday, December 21, 2006, 7:24:54 PM, you wrote:

> Hi,

> Today I seperated the thumb bits from
> conf/machine/include/ipx4xx.conf into
> conf/machine/include/. I'd like to enable for all >=v5t machines, but I'm unsure about
> using positive or negative logic.

  What about armv4t?

> * positive logic: might break for (soft)fpa distros that don't disable it, no problem for
> EABI distros
> * negative logic: no difference to status quo, but having negative logic in tune-* files
> feels a bit wrong.

  It's very nice to see ("real") thumb support being added to OE in
general! But I guess, it's too bold a step to switch to it be the
default. There're usual risk management issues (who knows what bugs
CPUs/software have regarding thumb), plus, thumb has known drawback of
reduced performance.

  In ideal case, thumb usage would be set per-package, with most
of libraries being normal code, and most apps - thumb (and in this
case thumb can be indeed the default).


> If you need numbers:
> http://ewi546.ewi.utwente.nl/tmp/thumb/comparison.txt (package:
> <thumb size> <regular size> (<unit>))

  Using ipk sizes is of course pretty heuristical ;-). IMHO, those
sizes are not too much convincing at all, but I'm sure raw exe sizes
are better, and striving for that ideal case is worthy task ;-)

> what do you all think?

> regards,

> Koen


-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  reply	other threads:[~2006-12-21 17:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-21 17:24 [RFC] Enable tune-thumb.inc for all armv5t and armv6t machines Koen Kooi
2006-12-21 17:44 ` Paul Sokolovsky [this message]
2006-12-21 18:21   ` Koen Kooi
2006-12-21 23:12     ` Paul Sokolovsky
2006-12-22  9:18       ` 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=1151969252.20061221194402@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=openembedded-devel@lists.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 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.