From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Cc: Andre McCurdy <andre.mccurdy@entropic.com>
Subject: Re: [meta-qt5] why does Qt5 build with ARM_INSTRUCTION_SET = "arm"
Date: Mon, 17 Feb 2014 16:46:23 -0500 [thread overview]
Message-ID: <20140217214623.GU22890@denix.org> (raw)
In-Reply-To: <CAP71Wjy4dxnDZFb3x_5zPg5HV-VOakeYtFz+8o0h2xk08R1=zQ@mail.gmail.com>
On Mon, Feb 17, 2014 at 02:27:51PM -0700, Nicolas Dechesne wrote:
> hi,
>
> does anybody know why in Qt5/qtbase.inc, we have:
>
> ARM_INSTRUCTION_SET = "arm"
>
> Could it be an a low hanging fruit from the past? e.g. before
> https://bugreports.qt-project.org/browse/QTBUG-16402 or
> https://qt.gitorious.org/qt/qtbase/commit/a3bd9d4c0f3d9e80dbe35bd88649b245dca5f410?
Hmm, I would assume that's here from 4.8 days, although I haven't tried
dropping that line for latest Qt5... Would make sense to do some more testing.
> as a matter of fact, for our project Qt5 (and QtWebkit) are building
> (and working fine) when built with Thumb2, outside of OE. Also using
> ARM instruction set instead of Thumb2 enforces Webkit to use the ARM
> version of the javascript JIT, while the Thumb2 JIT engine seems to
> work a lot better in our testing...
Seems like worth the effort to re-test the need for that setting. Unless
someone else has tried it already and found out the issue is still there
--
Denys
next prev parent reply other threads:[~2014-02-17 21:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 21:27 [meta-qt5] why does Qt5 build with ARM_INSTRUCTION_SET = "arm" Nicolas Dechesne
2014-02-17 21:46 ` Denys Dmytriyenko [this message]
2014-02-17 23:03 ` Martin Jansa
2014-02-18 5:33 ` Andre McCurdy
2014-02-18 6:56 ` Martin Jansa
2014-02-18 8:01 ` [meta-qt5][PATCH] qtbase.inc: don't force ARM_INSTRUCTION_SET to arm Andre McCurdy
2014-02-17 22:44 ` [meta-qt5] why does Qt5 build with ARM_INSTRUCTION_SET = "arm" Khem Raj
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=20140217214623.GU22890@denix.org \
--to=denis@denix.org \
--cc=andre.mccurdy@entropic.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.