Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH/RFC] qt4-embedded: tune QT_ARCH for armv6
Date: Fri, 05 Nov 2010 10:42:04 +0100	[thread overview]
Message-ID: <4CD3D16C.70901@eukrea.com> (raw)
In-Reply-To: <4CD3CF1E.4040804@freyther.de>

Hi,

Le 05/11/2010 10:32, Holger Freyther a écrit :
> On 11/04/2010 08:14 PM, Eric Bénard wrote:
>> in the painting engine, from what I saw in the .h, the asm optimisations are
>> only enabled when using ARM RCVT compiler and not when using gcc but I have
>> not checked everywhere in the code so I'm not sure of this.
>
> that is something else, I also have a partially applied C implementation that
> appears to be faster than the brute force armv6 code.
>
OK where is the code you are talking about in qt ?

> One benefit of using armv6 is that the atomic code will use a different
> implementation (ldrex,strex IIRC instead of swp). In any case please use
> something like qttracereply to see if passing armv6 is giving any benefit at all.
>
I can, do you have a quick howto run this ?

One thing : what I see here is that qtdemo was crashing after a random time 
and now (with armv6) it runs stable for hours.

Eric



  reply	other threads:[~2010-11-05  9:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-04  9:52 [PATCH/RFC] qt4-embedded: tune QT_ARCH for armv6 Eric Bénard
2010-11-04 18:05 ` Khem Raj
2010-11-04 18:26 ` Holger Freyther
2010-11-04 19:14   ` Eric Bénard
2010-11-05  9:32     ` Holger Freyther
2010-11-05  9:42       ` Eric Bénard [this message]
2010-11-05 10:21         ` Holger Freyther
2010-11-05 10:41           ` Eric Bénard
2010-11-07 19:42           ` Eric Bénard
2010-11-04 20:27   ` Khem Raj
2010-11-04 21:05   ` Koen Kooi
2010-11-05 11:21   ` Phil Blundell

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=4CD3D16C.70901@eukrea.com \
    --to=eric@eukrea.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox