[Bug 340106]

2020-02-15 Thread Thiago Macieira
(In reply to Harald Sitter from comment #7) > Thanks. > > With that in mind we cannot really support spaces while also following the > smb URI format [1]. I suppose we'll just have to deviate a bit iff the > workgroup name contains a space by using a variant of the notation that > stuffs the workg

[Bug 340106]

2020-02-15 Thread Thiago Macieira
QUrl's behaviour is intentional. The hostname component of the URL has to be a valid hostname. Do not store anything in that component that is not a hostname. Like a workgroup name. Store that elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subs

[Bug 490371] Re: Atomic operations not safe for ARMv7, Thumb-2 and multicore

2010-12-08 Thread Thiago Macieira
Please submit the patch upstream: http://bugreports.qt.nokia.com, product Qt, component Threading. -- 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/490371 Title: Atomic operations not safe

[Bug 664431] Re: QT on armel is built with NEON by default

2010-12-03 Thread Thiago Macieira
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 subsc

[Bug 664431] Re: QT on armel is built with NEON by default

2010-12-02 Thread Thiago Macieira
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 problem

[Bug 664431] Re: QT on armel is built with NEON by default

2010-12-01 Thread Thiago Macieira
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

[Bug 664431] Re: QT on armel is built with NEON by default

2010-11-30 Thread Thiago Macieira
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

Re: [Bug 490371] [NEW] Atomic operations not safe for ARMv7, Thumb-2 and multicore

2010-11-19 Thread Thiago Macieira
tring.cpp 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 -- Thiago Macieira - thiago.macieira (AT) nokia.com Senior Product Manager - Nokia, Qt Development Frameworks Sandakerveien 116, NO-040

[Bug 673085] Re: Qt/KDE fails to build on ARM without implicit-it=thumb

2010-11-15 Thread Thiago Macieira
Unless __sync now supports the four memory ordering semantics, the patch will not be accepted upstream. -- Qt/KDE fails to build on ARM without implicit-it=thumb https://bugs.launchpad.net/bugs/673085 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed

Re: [Bug 664431] Re: QT on armel is built with NEON by default

2010-11-09 Thread Thiago Macieira
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 M

Re: [Bug 664431] Re: QT on armel is built with NEON by default

2010-11-09 Thread Thiago Macieira
.obj/release-shared/qsimd.o tools/qsimd.cpp See the -mfpu=neon there. I think I see the problem. It's upstream. -- Thiago Macieira - thiago.macieira (AT) nokia.com Senior Product Manager - Nokia, Qt Development Frameworks Sandakerveien 116, NO-0402 Oslo, Norway -- QT on armel is b

Re: [Bug 664431] Re: QT on armel is built with NEON by default

2010-11-08 Thread Thiago Macieira
like there was a detection mistake. Can you try turning the feature off by setting QT_NO_CPU_FEATURE=neon and running the app again? Finally, it would be nice also to have the command-line of the compiler used when compiling the actual .cpp file. -- Thiago Macieira - thiago.macieira (AT) nokia.com

Re: [Bug 664431] Re: QT on armel is built with NEON by default

2010-10-29 Thread Thiago Macieira
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. -- T

Re: [Bug 664431] Re: QT on armel is built with NEON by default

2010-10-28 Thread Thiago Macieira
Oh, that might explain it all. The fix wasn't cherry-picked into the 4.7.0 release. Just take the two qsimd files and it should be your patch: http://qt.gitorious.org/qt/qt/blobs/4.7/src/corelib/tools/qsimd.cpp http://qt.gitorious.org/qt/qt/blobs/4.7/src/corelib/tools/qsimd_p

[Bug 664431] Re: QT on armel is built with NEON by default

2010-10-28 Thread Thiago Macieira
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 dete