this is an ubuntu build time issue, doesnt affect upstream Qt, closing
this task as invalid
** Changed in: qt
Status: New = Invalid
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
I am having the same problem on the Lucid version of armel with Qt 4.6.2
Is a backport planned for this since we can't upgrade to Qt 4.7 which breaks
several applications?
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
No backport is contemplated. Backporting Qt breaks too many applications.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in Ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by default
--
** Changed in: qt4-x11 (Ubuntu Natty)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by default
--
just to confirm, works fine on the ac100 (tegra2 no neon) using unity-2d
here in natty
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by
The package has built, it needs testing on non-NEON hw.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by default
--
kubuntu-bugs mailing
** Changed in: qt4-x11 (Ubuntu Natty)
Status: Triaged = In Progress
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by default
--
Unpatched Qt 4.7.2 FTBFS as -mfpu=neon is not passed to two cpp files
(painting/drawhelper_neon.cpp and image/qimage_neon.cpp) .
This fixes it but it needs better variable naming probably, I just went
for minimal number of lines changed.
Index: qt4-x11-4.7.2/src/gui/gui.pro
** Changed in: qt4-x11 (Ubuntu Natty)
Assignee: Oliver Grawert (ogra) = Jani Monoses (jani)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is built with NEON by
** Summary changed:
- QT on armel is built with NEON by default
+ Qt on armel is built with NEON by default
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
Qt on armel is
The upstream bug is marked as fixed and part of the upcoming 4.7.2
release. Hopefully that will fix this for natty.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
QT on
** Tags added: arm-porting-queue
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
https://bugs.launchpad.net/bugs/664431
Title:
QT on armel is built with NEON by default
--
kubuntu-bugs mailing list
In this case, can we disable the NEON optimization code in qstring.cpp
temporarily? I checked latest qstring.cpp, and there is only NEON for
QString::fromLatin1_helper() function.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Like I explained, the code is enabled if and only if qstring.cpp is
compiled with -mfpu=neon. We don't turn that on anymore, ever.
If you want that option, you need to set the configure flags yourself.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
@Thiago
Huh? I don't get it. I haven't looked at the code (bugdiffs is down atm), but
don't you need to do the run-time detection only once? Or is a simple compare
and branch too much of a perfirmance hit?
Just curious.
--
You received this bug notification because you are a member of Kubuntu
Sorry, let me be more specific:
1) there's a problem with the configure-time code that detects whether
the compiler supports Neon intrinsics. Somehow, MeeGo managed to get a
false positive here and configure decides that the compiler doesn't
support Neon. This is not fixed.
2) there was a
That's already so:
$ git ls-files *_neon*
src/gui/image/qimage_neon.cpp
src/gui/painting/qdrawhelper_neon.cpp
src/gui/painting/qdrawhelper_neon_asm.S
src/gui/painting/qdrawhelper_neon_p.h
These files are the ones that contain 99% of the Neon code in Qt and
they're properly
guys, couldnt you try to fix the build system to not pass -mfpu=neon if
neon is detected, but still include arm_neon.h ... which i assume will
enable the manually coded neon paths depending on whether the hw feature
is on the host?
if that wasnt tried, please consider to do that before regressing
subscribed a few folks from linaro graphics WG ... maybe they can help
here if they have some cycles.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in
Agreed.
Our official enablement this cycle is for NEON _enabled_ platforms only.
Whilst supporting non-NEON boards is an eventual goal it should not be
at the detriment of the platforms we have committed to for Natty.
--
QT on armel is built with NEON by default
this bug is about a maverick SRU where ubuntu fully supports non NEON
architectures, we will upload the static fix to natty too during this
week until the upstream fixes are done. given there is no movement
upstream yet and the SRU team expects the fix to be in natty as well for
accepting it into
This is going to hurt users of neon capable systems (which is almost
everyone). I don't think this SRU is consistent with Ubuntu policy.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Ubuntu
Bugs,
The archive is supposed to support the entire ARMv7 class of devices,
and in that class of devices NEON was/is optional we can only have run
time support for NEON, not statically hard compiled in. What devices
we directly support can change even now, so any statically hard compiled
in NEON
Scott Kitterman [2010-11-30 13:15 -]:
I don't think this SRU is consistent with Ubuntu policy.
I accepted it under the premise that it is a regression from lucid
(read: all Qt applications crash right away with a SIGILL). It
happens on a dove board I have laying around, but I don't know how
The Dove board is a supported platform and is one of the ARMv7 class
platforms that does not support NEON. Martin you have made the correct
choice, it is indeed a regression from lucid. All NEON support in the
archive must be run time detected to make sure the CPU in question can
actually
I support entirely David's position: we committed to delivering an
userspace not requiring NEON, independently from the binary kernels or
the images directly in Ubuntu. This is true of both maverick and lucid.
The fact that the whole of Qt was built with NEON is a bug, and there is
no doubt that
There are multiple ways to deal with the speed regression, in a second step:
a) we could arrange for an armel PPA with a Qt rebuilt with NEON (this is
true of any package BTW); this requires special permission, and ongoing
maintenance, but Qt isn't updated frequently in stable releases.
b)
On Tue, Nov 30, 2010 at 11:58 AM, Oliver Grawert o...@ubuntu.com wrote:
There are multiple ways to deal with the speed regression, in a second step:
a) we could arrange for an armel PPA with a Qt rebuilt with NEON (this is
true of any package BTW); this requires special permission, and ongoing
On Tue, Nov 30, 2010 at 11:15 AM, Scott Kitterman ubu...@kitterman.com wrote:
This is going to hurt users of neon capable systems (which is almost
everyone). I don't think this SRU is consistent with Ubuntu policy.
It is going to hurt users of neon capable systems, and it's a post
release
I understand it's a regression for some hardware from Lucid. This SRU is a
regression for a different set of hardware. That's mitigated by the PPA
packages that are being provided, but I think it's a reasonably novel
interpretation of our SRU policy to tell users that had reasonably working
My recommendation (as upstream) is that you compile Qt with run-time-
detected Neon support. That is, do not enable -mfpu=neon everywhere, but
let Qt detect that the compiler supports this option and enable only for
the *_neon.cpp files.
I knew that Qt had this supported at UDS, but what I didn't
** Changed in: qt4-x11 (Ubuntu Natty)
Milestone: None = ubuntu-11.04-beta
** Changed in: qt4-x11 (Ubuntu Natty)
Importance: Undecided = High
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of
This bug was fixed in the package qt4-x11 - 4:4.7.0-0ubuntu4.2
---
qt4-x11 (4:4.7.0-0ubuntu4.2) maverick-proposed; urgency=low
* disable NEON on armel builds (LP: #664431)
-- Oliver Grawert o...@ubuntu.com Thu, 21 Oct 2010 14:45:54 +0200
** Changed in: qt4-x11 (Ubuntu Maverick)
** Changed in: qt4-x11 (Ubuntu Natty)
Status: Confirmed = Triaged
** Changed in: qt4-x11 (Ubuntu Natty)
Assignee: (unassigned) = Oliver Grawert (ogra)
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you
after a discussion on IRC we decided that we will not apply the static
non-NEON build to natty for now to give upstream the opportunity for a
proper fix of the runtime detection.
If this fix is not available by natty beta either option a) or option b)
from comment #50 above will be implemented.
Ok, for Natty no PPA will be provided for now as it'll just FTBFS
anyway. The idea for Natty is to get the proper fix from upstream and be
able to do runtime detection.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because
Am Dienstag, den 30.11.2010, 14:24 + schrieb Scott Kitterman:
I understand it's a regression for some hardware from Lucid. This SRU is a
regression for a different set of hardware. That's mitigated by the PPA
packages that are being provided, but I think it's a reasonably novel
I think we need to centralize all NEON asm code in one or several files,
and build these source files with -mfpu=neon option, but for other
files, -mfpu=neon option should not be used when compiling.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received
Please get this fixed in natty (one way or the other), so that the fix
can proceed to maverick-updates.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11
installing mumble (QT app) on a NEON-less tegra2 system with the
4.7.0-0ubuntu4.2 QT packages from maverick-proposed works fine, no
SIGILL, app starts and is functional
** Tags added: verification-done
** Tags removed: verification-needed
--
QT on armel is built with NEON by default
** Tags added: kubuntu
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bugs mailing list
kubuntu-b...@lists.ubuntu.com
On Fri, Nov 19, 2010 at 2:44 PM, Ricardo Salveti rsalv...@rsalveti.net wrote:
I'll make a public PPA available with the neon compatible Qt, so people
can continue using the released version with neon accelerated pieces.
Qt PPA with NEON enabled: https://launchpad.net/~rsalveti/+archive/qt-
neon
given that there is not much movement yet on the upstream bug, i re-
uploaded 4.7.0-0ubuntu4.1 that disables NEON statically. so people
without NEON finally can use QT apps. once the upstream fix is found and
implemented i'm happy to revert the change again for dynamic runtime
NEON detection.
SRU
i bumped the version to ubuntu4.2 since there is a 4.1 source in the
archive already, sorry for the inconvenience
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed
I'll make a public PPA available with the neon compatible Qt, so people
can continue using the released version with neon accelerated pieces.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Accepted qt4-x11 into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: qt4-x11 (Ubuntu
** Also affects: qt
Importance: Undecided
Status: New
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bugs mailing
Em Segunda-feira 08 Novembro 2010, às 19:40:34, você escreveu:
One example:
g++ -c -include .pch/release-shared/QtCore -g -O2
-I/usr/include/freetype2 -pthread -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -mfpu=neon -O2 -fvisibility=hidden
-fvisibility-inlines-hidden -Wall -W
Em Terça-feira 09 Novembro 2010, às 10:27:16, você escreveu:
See the -mfpu=neon there.
I think I see the problem. It's upstream.
Upstream report created:
http://bugreports.qt.nokia.com/browse/QTBUG-15150
--
Thiago Macieira - thiago.macieira (AT) nokia.com
Senior Product Manager - Nokia,
** Changed in: qt4-x11 (Ubuntu Natty)
Status: New = Confirmed
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
testing the packages from ricardos PPA on a non NEON architecture
results in a SIGILL again :(
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in
Em Segunda-feira 08 Novembro 2010, às 16:50:52, você escreveu:
testing the packages from ricardos PPA on a non NEON architecture
results in a SIGILL again :(
Can you post a backtrace? It would be useful if the build used -fno-inline, or
this will get a bit tricky to track down.
Please also
r...@ac100:~# /usr/lib/libQtCore.so.4.7.0
This is the QtCore library version 4.7.0
Copyright (C) 2010 Nokia Corporation and/or its subsidiary(-ies).
Contact: Nokia Corporation (qt-i...@nokia.com)
Build key: armv6 linux g++-4 full-config
Build date: 2010-11-04
Installation
On Mon, Nov 8, 2010 at 2:09 PM, Thiago Macieira
664...@bugs.launchpad.net wrote:
Em Segunda-feira 08 Novembro 2010, às 16:50:52, você escreveu:
testing the packages from ricardos PPA on a non NEON architecture
results in a SIGILL again :(
Can you post a backtrace? It would be useful if the
Removed qt4-x11 4:4.7.0-0ubuntu4.1 from maverick-proposed due to the
regression. Please upload this fixed version with runtime detection
support when you have a chance.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because
@Richard,
Are QT_HAVE_IWMMXT and QT_HAVE_NEON mutually exclusive?
Currently, if QT_HAVE_IWMMXT _or_ QT_HAVE_NEON is set to 1, this causes
both features to be suppressed, which may not be what is desired if both
extensions can be enabled in a general-purpose bulid.
Maybe something like this:
@Dave: this was basically the previous behavior, that I didn't want to
change because it's outside the scope of this bug.
From current Qt in Maverick:
...
#elif defined(QT_HAVE_IWMMXT)
// runtime detection only available when running as a previlegied process
static const bool doIWMMXT =
Was finally able to build a new qt package with the attached patch.
Oliver, in case you want to test please get the packages from our
private PPA, or wait the packages to be copied to my own public PPA at
https://launchpad.net/~rsalveti/+archive/armel.
Please test it at your AC100 and let us know
I ported the following patch to have NEON autodetection. It's basically
the same logic as upstream, but without putting NEON as default in case
it cant find /proc/self/auxv. It also allows the user to run without
NEON, by exporting QT_NO_NEON.
I'm currently trying to build the Qt package with
if i read that code right it enforces NEON use if it cant open /proc/self/auxv
...
sorry, but thats not acceptable, it should use a conservative default instead,
can that be changed ?
otherwise the patch looks fine
--
QT on armel is built with NEON by default
On Friday, 29 de October de 2010 07:22:28 you wrote:
if i read that code right it enforces NEON use if it cant open
/proc/self/auxv ... sorry, but thats not acceptable, it should use a
conservative default instead, can that be changed ?
Yes, I think it's a good idea.
--
Thiago Macieira -
** Changed in: qt4-x11 (Ubuntu Maverick)
Status: Fix Committed = In Progress
** Changed in: qt4-x11 (Ubuntu Maverick)
Assignee: Oliver Grawert (ogra) = Ricardo Salveti (rsalveti)
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this
This is the actual commit that introduces runtime verification of processor
features on ARM:
http://qt.gitorious.org/qt/qt/commit/5070c3ae331faf18f6997535356853cc61ef0ad7
It was introduced before Qt 4.7.0rc1 so the Ubuntu build should have it.
Therefore, there are two possibilities:
1) the
On Thu, Oct 28, 2010 at 9:09 AM, Thiago Macieira thi...@kde.org wrote:
This is the actual commit that introduces runtime verification of processor
features on ARM:
http://qt.gitorious.org/qt/qt/commit/5070c3ae331faf18f6997535356853cc61ef0ad7
It was introduced before Qt 4.7.0rc1 so the
On Thursday, 28 de October de 2010 07:55:34 you wrote:
I currently can't get the git code (download at 8k/s), so I checked
the 4.7.0 release tarball and this commit doesn't seems to be
included:
$ vim qt-everywhere-opensource-src-4.7.0/src/corelib/tools/qsimd.cpp
---
#elif
could someone point to the matching commit so we can see the impact ?
i dont think we actually care in which way neon is disabled on platforms that
dont support it as long as you dont get a SIGILL for all QT apps you try to
start.
platforms that support NEON will indeed benefit from it but we
Marking as v-failed for now. Keeping in -proposed is fine, since the
performance regression isn't really breaking anything. From the recent
comments it seems it should be possible to fix the runtime detection, so
I agree that this would be the better approach.
** Tags added: verification-failed
On 27.10.2010 01:58, Scott Kitterman wrote:
Steve Langaseksteve.langa...@canonical.com wrote:
it is a performance regression on some hardware, in exchange for
correcting a regression in basic functionality of the package on other
supported hardware. In the absence of other solutions, I
This would be a post release regression for hardware that has NEON
support. Is this really appropriate for an SRU?
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed
it is a performance regression on some hardware, in exchange for
correcting a regression in basic functionality of the package on other
supported hardware. In the absence of other solutions, I think this is
preferable over the status quo. Do you disagree?
--
QT on armel is built with NEON by
Talking with Thiago Macieira at UDS he said that Qt already has auto
detection for NEON at upstream. Maybe we can identify the proper commit
and just backport the fix, then we'll have the best of both worlds.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You
My understanding is it's fixed in 4.7.1 so it should be manageable for
someone to dig the proper fix out of Qt got.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed
Steve Langasek steve.langa...@canonical.com wrote:
it is a performance regression on some hardware, in exchange for
correcting a regression in basic functionality of the package on other
supported hardware. In the absence of other solutions, I think this is
preferable over the status quo. Do
*** This bug is a duplicate of bug 600154 ***
https://bugs.launchpad.net/bugs/600154
** This bug has been marked a duplicate of bug 600154
[arm] Don't build with neon instructions support on arm
* You can subscribe to bug 600154 by following this link:
** This bug is no longer a duplicate of bug 600154
[arm] Don't build with neon instructions support on arm
** Changed in: qt4-x11 (Ubuntu Maverick)
Assignee: (unassigned) = Oliver Grawert (ogra)
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You
a fix for this issue was uploaded to maverick-poposed, SRU team, please
approve
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
qt4-x11 (4:4.7.0-0ubuntu4.1) maverick-proposed; urgency=low
* disable NEON on armel builds (LP: #664431)
-- Oliver Grawert o...@ubuntu.com Thu, 21 Oct 2010 14:45:54 +0200
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification
Accepted qt4-x11 into maverick-proposed, the package will build now and
be available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: qt4-x11 (Ubuntu
** Branch linked: lp:ubuntu/maverick-proposed/qt4-x11
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
kubuntu-bugs mailing list
Hello,
There is already a way to disable NEON on runtime as you can see in the
following commit in qt.
http://qt.gitorious.org/qt/qt/commit/ebf9d5dd5174b7c82fec83b56d71a59d5277bd51
export QT_NO_CPU_FEATURE=neon
How could we properly use this feature?
--
QT on armel is built with NEON by
Is it possible to enable it at runtime? Because by default we should
avoid using NEON.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to qt4-x11 in ubuntu.
--
And the best option for us would be automatic detection at runtime, so
we don't need to use any env variable. It seems Linaro is working on
that, but don't know if that's ready already.
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug
http://www.llvm.org/bugs/attachment.cgi?id=4428 is an example how to do
runtime NEON detection through hwcaps (using /proc/self/auxv)
--
QT on armel is built with NEON by default
https://bugs.launchpad.net/bugs/664431
You received this bug notification because you are a member of Kubuntu
Bugs,
83 matches
Mail list logo
