Re: [Development] Updating x86 SIMD support in Qt

2022-03-23 Thread Thiago Macieira
On Wednesday, 23 March 2022 20:34:07 -03 Volker Hilsheimer wrote:
> I have a possibly wrong hunch that building Qt Multimedia fails because of
> this. This is in a Ubuntu 20.04 VM in the VMware Fusion 12 provider, and
> the hardware version is maxed out (it wasn’t earlier, but didn’t help to
> put it to level 18). So there’s not a whole lot I can do on the VM
> provisioning side, I think.

> /home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../
> ../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:256:8: error: #error
> "Please enable all x86-64-v3 extensions; you probably want to use
> -march=haswell or -march=x86-64-v3 instead of -mavx2"

> /home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../
> ../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:81: error:
> ‘__FMA__’ was not declared in this scope> 

By the way, please note that VirtualBox enables AVX2 but not FMA and some of 
the other required functionality for x86-64-v3. So a VirtualBox environment is 
*not* x86-64-v3 and therefore you cannot run such binaries and you cannot 
compile Qt with -march=native in it.

As far as I know, this is a problem exclusive to VirtualBox. It wouldn't 
affect VMWare or qemu KVM-accelerated virtualisation. I also haven't noticed 
it on Parallels on my Mac. It's been reported but hasn't been fixed.

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel DPG Cloud Engineering



___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Updating x86 SIMD support in Qt

2022-03-23 Thread Volker Hilsheimer


> On 24 Mar 2022, at 00:34, Volker Hilsheimer  wrote:
> 
>> On 24 Jan 2022, at 17:04, Thiago Macieira  wrote:
>> 
>> On Monday, 24 January 2022 05:30:46 PST Konrad Rosenbaum wrote:
>>> I have absolutely no problem with stuff running faster and more
>>> efficient on my two laptops (which are significantly more modern), but I
>>> would have a major problem with it not running at all on my workstation
>>> that I use for 95% of all my Open Source work. And I would also not like
>>> my applications to crash on my downstream user's computers (which are on
>>> average just as old as mine) - every crash means hours of work for
>>> someone (usually me) to find out what the problem was.
>> 
>> At least i can promise you not to make it a silent crash. Either QtCore or 
>> the 
>> dynamic linker would say it can't run on that machine.
>> 
>> https://code.woboq.org/qt6/qtbase/src/corelib/global/
>> qsimd.cpp.html#_Z16qDumpCPUFeaturesv
> 
> I have a possibly wrong hunch that building Qt Multimedia fails because of 
> this. This is in a Ubuntu 20.04 VM in the VMware Fusion 12 provider, and the 
> hardware version is maxed out (it wasn’t earlier, but didn’t help to put it 
> to level 18). So there’s not a whole lot I can do on the VM provisioning 
> side, I think.
> 
> Volker
> 


Nevermind, my dev branch wasn’t rebased.

Time to hit the hay, evidently.

Cheers,
Volker

___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development


Re: [Development] Updating x86 SIMD support in Qt

2022-03-23 Thread Volker Hilsheimer
> On 24 Jan 2022, at 17:04, Thiago Macieira  wrote:
> 
> On Monday, 24 January 2022 05:30:46 PST Konrad Rosenbaum wrote:
>> I have absolutely no problem with stuff running faster and more
>> efficient on my two laptops (which are significantly more modern), but I
>> would have a major problem with it not running at all on my workstation
>> that I use for 95% of all my Open Source work. And I would also not like
>> my applications to crash on my downstream user's computers (which are on
>> average just as old as mine) - every crash means hours of work for
>> someone (usually me) to find out what the problem was.
> 
> At least i can promise you not to make it a silent crash. Either QtCore or 
> the 
> dynamic linker would say it can't run on that machine.
> 
> https://code.woboq.org/qt6/qtbase/src/corelib/global/
> qsimd.cpp.html#_Z16qDumpCPUFeaturesv

I have a possibly wrong hunch that building Qt Multimedia fails because of 
this. This is in a Ubuntu 20.04 VM in the VMware Fusion 12 provider, and the 
hardware version is maxed out (it wasn’t earlier, but didn’t help to put it to 
level 18). So there’s not a whole lot I can do on the VM provisioning side, I 
think.

Volker



In file included from 
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/qsimd_p.h:1,
 from 
/home/vagrant/qt/dev/qtmultimedia/src/multimedia/video/qvideoframeconversionhelper_p.h:55,
 from 
/home/vagrant/qt/dev/qtmultimedia/src/multimedia/video/qvideoframeconversionhelper_avx2.cpp:40:
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:256:8:
 error: #error "Please enable all x86-64-v3 extensions; you probably want to 
use -march=haswell or -march=x86-64-v3 instead of -mavx2"
  256 | #  error "Please enable all x86-64-v3 extensions; you probably want 
to use -march=haswell or -march=x86-64-v3 instead of -mavx2"
  |^
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:49:
 error: ‘__BMI__’ was not declared in this scope
  253 | #  define ARCH_HASWELL_MACROS   (__AVX2__ + __BMI__ + __BMI2__ + 
__F16C__ + __FMA__ + __LZCNT__)
  | ^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:258:15:
 note: in expansion of macro ‘ARCH_HASWELL_MACROS’
  258 | static_assert(ARCH_HASWELL_MACROS, "Undeclared identifiers indicate 
which features are missing.");
  |   ^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:59:
 error: ‘__BMI2__’ was not declared in this scope
  253 | #  define ARCH_HASWELL_MACROS   (__AVX2__ + __BMI__ + __BMI2__ + 
__F16C__ + __FMA__ + __LZCNT__)
  |   ^~~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:258:15:
 note: in expansion of macro ‘ARCH_HASWELL_MACROS’
  258 | static_assert(ARCH_HASWELL_MACROS, "Undeclared identifiers indicate 
which features are missing.");
  |   ^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:70:
 error: ‘__F16C__’ was not declared in this scope
  253 | #  define ARCH_HASWELL_MACROS   (__AVX2__ + __BMI__ + __BMI2__ + 
__F16C__ + __FMA__ + __LZCNT__)
  |  
^~~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:258:15:
 note: in expansion of macro ‘ARCH_HASWELL_MACROS’
  258 | static_assert(ARCH_HASWELL_MACROS, "Undeclared identifiers indicate 
which features are missing.");
  |   ^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:81:
 error: ‘__FMA__’ was not declared in this scope
  253 | #  define ARCH_HASWELL_MACROS   (__AVX2__ + __BMI__ + __BMI2__ + 
__F16C__ + __FMA__ + __LZCNT__)
  | 
^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:258:15:
 note: in expansion of macro ‘ARCH_HASWELL_MACROS’
  258 | static_assert(ARCH_HASWELL_MACROS, "Undeclared identifiers indicate 
which features are missing.");
  |   ^~~
/home/vagrant/dev-build/qtbase/include/QtCore/6.4.0/QtCore/private/../../../../../../../qt/dev/qtbase/src/corelib/global/qsimd_p.h:253:91:
 error: 

[Development] [Announce] Qt Creator 7 released

2022-03-23 Thread List for announcements regarding Qt releases and development via Development
We are happy to announce the release of Qt Creator 7!

https://www.qt.io/blog/qt-creator-7-released

-- 
Eike Ziller
Principal Software Engineer

The Qt Company GmbH
Erich-Thilo-Straße 10
D-12489 Berlin
eike.zil...@qt.io
http://qt.io
Geschäftsführer: Mika Pälsi,
Juha Varelius, Jouni Lintunen
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 
144331 B


___
Announce mailing list
annou...@qt-project.org
https://lists.qt-project.org/listinfo/announce
___
Development mailing list
Development@qt-project.org
https://lists.qt-project.org/listinfo/development