From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] qt - fix execution on ARC
Date: Sat, 11 Jul 2015 00:56:52 +0200 [thread overview]
Message-ID: <20150711005652.1bb5ff0f@free-electrons.com> (raw)
In-Reply-To: <1432620833-5698-1-git-send-email-abrodkin@synopsys.com>
Dear Alexey Brodkin,
On Tue, 26 May 2015 09:13:53 +0300, Alexey Brodkin wrote:
> Even though Qt4 could be built for ARC cores during execution
> of Qt4 applications on target issues will happen.
>
> Most notable is will be segfaults due to unaligned access to data,
> especially in WebKit applications.
>
> Both patches were submitted upstream and if they ever get accepted
> they should be removed from Buildroot.
>
> https://codereview.qt-project.org/#/c/112667
> https://codereview.qt-project.org/#/c/112668
>
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> Cc: Anton Kolesov <akolesov@synopsys.com>
> Cc: Vineet Gupta <vgupta@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> ...9-Add-initial-support-of-ARC-architecture.patch | 183 +++++++++++++++++++++
> .../qt/0010-Prevent-unaligned-access-on-ARC.patch | 92 +++++++++++
> 2 files changed, 275 insertions(+)
> create mode 100644 package/qt/0009-Add-initial-support-of-ARC-architecture.patch
> create mode 100644 package/qt/0010-Prevent-unaligned-access-on-ARC.patch
I've adjusted the commit title (qt: fix execution on ARC), renumbered
the patches and applied. Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-07-10 22:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 6:13 [Buildroot] [PATCH] qt - fix execution on ARC Alexey Brodkin
2015-07-10 22:56 ` 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=20150711005652.1bb5ff0f@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.