Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Tuesday, 18 January 2022 19:01:06 PST Thiago Macieira wrote: > 4) up the defaults from where they are today > > Today, your default Qt build will always target the x86-64 baseline[*], > including for i386, despite as I said no CPU failing to meet the next level > for 9 years. I'd like to

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 08:48:37 PST Thiago Macieira wrote: > If Microsoft wants their OS to have better-performing content, they'll have > to come up with a solution. I do plan to reach out to them via the team > that works with them at Intel, but I don't expect to see any solution, at >

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Jukka Jokiniva
+1 from me too --Jukka From: Development on behalf of Oliver Eftevaag Date: Wednesday, 19. January 2022 at 16.01 To: Mårten Nordheim , Volker Hilsheimer , development@qt-project.org Subject: Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver +1  Oliver Eftevaag

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Kevin Kofler via Development
Thiago Macieira wrote: > Whether Fedora decides to up the minimum requirement for a future edition > is something you'll be in a better position to answer than I am. So far, I and few others have successfully blocked attempts at upping the minimum requirement for Fedora. (The requirement for the

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 14:03:41 PST Kevin Kofler via Development wrote: > Thiago Macieira wrote: > > Clear Linux attempts to use a heuristic to guess which libraries it thinks > > are worth keeping the AVX2 version of. To see which ones it thought of > > qtbase, see

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 13:52:21 PST Kevin Kofler via Development wrote: > The notebook has 4 GiB RAM. (That was the maximum available. I picked it > because I wanted the notebook to last.) Fedora 35 with KDE Plasma runs fine > on it. Not fast, but usable. Whether Fedora decides to up the

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Kevin Kofler via Development
Thiago Macieira wrote: > Clear Linux attempts to use a heuristic to guess which libraries it thinks > are worth keeping the AVX2 version of. To see which ones it thought of > qtbase, see https://github.com/clearlinux-pkgs/qtbase/blob/ >

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Kevin Kofler via Development
Thiago Macieira wrote: > I understand. I have one of those in a cabinet, but it doesn't power on > (the PSU is bust). My notebook's power supply adapter went bust in 2019, but thankfully, the circuitry inside the notebook is fine, only the external adapter had broken down. So I replaced it with

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 08:55:46 PST Thiago Macieira wrote: > I'm not proposing we change Xcode project file generation. Only Qt's own > CMake-based build. I've just tried an x86_64h;arm64 universal build and it failed because of the ARM build. There's something wrong with my SDK or

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 09:51:38 PST Alexandru Croitor wrote: > > On 19. Jan 2022, at 18:34, Thiago Macieira > > wrote: > > > > Indeed. I'm hoping it's a matter of making qt_internal_add_module() > > creating two CMake targets instead of one, and modifying the C and C++ > > compiler flags

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 09:28:40 PST Edward Welbourne wrote: > Thiago Macieira (19 January 2022 17:48) replied: > > That's a misconception. AVX and especially AVX2 introduce a lot of > > codegen opportunities for the compilers, which they've been able to > > use for years. > > Is the

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Alexandru Croitor
> On 19. Jan 2022, at 18:34, Thiago Macieira wrote: > > Indeed. I'm hoping it's a matter of making qt_internal_add_module() creating > two CMake targets instead of one, and modifying the C and C++ compiler flags > as well as output dir for one of them. Which library names appear in the

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Allan Sandfeld Jensen
On Mittwoch, 19. Januar 2022 16:41:11 CET Thiago Macieira wrote: > On Tuesday, 18 January 2022 22:43:40 PST Kevin Kofler via Development wrote: > > Thiago Macieira wrote: > > > By default, I'd like us to produce x86-64 v2 code, which is SSE4. > > > > But v1 will still be available for

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 00:57:04 PST Alexandru Croitor wrote: > I believe this will pessimize optimisations for certain platforms as pointed > out in the linked change. > > Specifically QNX and iOS simulator builds. > >

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Edward Welbourne
On Wednesday, 19 January 2022 00:13:32 PST Lars Knoll wrote: >> AVX is only used by a couple of classes in Qt Core and the drawhelper >> in Qt Gui. Qt Gui already does runtime detection, so it would be only >> about adding that to the methods in Qt Core. Thiago Macieira (19 January 2022 17:48)

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 04:23:22 PST Allan Sandfeld Jensen wrote: > On Mittwoch, 19. Januar 2022 04:01:06 CET Thiago Macieira wrote: > > 5) for glibc-based Linux, add v3 sub-arch by default > > > > I'd like to raise the default on Linux from baseline to v2 *and* add a v3 > > sub- arch

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 05:04:07 PST Tor Arne Vestbø wrote: > Hey hey, > > On 19 Jan 2022, at 04:01, Thiago Macieira > mailto:thiago.macie...@intel.com>> wrote: > 3) add a way to have multi-arch glibc-based Linux builds > > If we go down this road I ask that we align both the porcelain

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Jean-Michaël Celerier
Re. wasm, as far as I know it's 32-bit (not x86 at all) but with a compatibility layer provided by emscripten which allows sse & avx intrinsincs to be translated to either equivalent vector instructions in the wasm bytecode, or shims which do it manually. Cheers, --

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Wednesday, 19 January 2022 00:13:32 PST Lars Knoll wrote: > The main thing I’m wondering about is how much performance we gain by from a > multi arch build Qt for different x86_64 architectures opposed to building > maybe for v2 and detecting/using AVX and AVX512 at runtime. I would assume >

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Tuesday, 18 January 2022 22:43:40 PST Kevin Kofler via Development wrote: > Thiago Macieira wrote: > > By default, I'd like us to produce x86-64 v2 code, which is SSE4. > > But v1 will still be available for distribution packaging? As long as that > is the case, I do not see a major issue, it

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Thiago Macieira
On Tuesday, 18 January 2022 20:56:10 PST Lorn Potter wrote: > wasm is a special case, as we turn it off by default, regardless of > detection. We cannot allow detection by default (specified by some > configure argument which is currently -sse2) because browsers do not > support it by default, and

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Oliver Eftevaag
+1  Oliver Eftevaag Software Engineer Graphics and UI The Qt Company Sandakerveien 116 0484, Oslo, Norway oliver.eftev...@qt.io +4746446690 http://qt.io From: Development on behalf of Mårten Nordheim Sent:

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Mårten Nordheim
+1 for sure Mårten From: Development on behalf of Volker Hilsheimer Sent: Wednesday, January 19, 2022 12:59 To: development@qt-project.org Subject: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver Hi, I’d like to nominate Dimitrios

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Tor Arne Vestbø
Hey hey, On 19 Jan 2022, at 04:01, Thiago Macieira mailto:thiago.macie...@intel.com>> wrote: 3) add a way to have multi-arch glibc-based Linux builds If we go down this road I ask that we align both the porcelain and plumbing (configure, build system, C++ APIs, etc) . We already have

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Paul Wicking
+1! //! Paul > On 19 Jan 2022, at 12:59, Volker Hilsheimer wrote: > > Hi, > > I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt > Project. > > Jimis has been working as a Software Engineer in the Qt Company since 2019 > and has made a number of contributions [0]

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Allan Sandfeld Jensen
On Mittwoch, 19. Januar 2022 04:01:06 CET Thiago Macieira wrote: > 5) for glibc-based Linux, add v3 sub-arch by default > > I'd like to raise the default on Linux from baseline to v2 *and* add a v3 > sub- arch build, as described by point #3 above. > > Device-specific Qt builds (Yocto Project,

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Shawn Rutledge
> On 2022 Jan 19, at 12:59, Volker Hilsheimer wrote: > > Hi, > > I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt > Project. > > Jimis has been working as a Software Engineer in the Qt Company since 2019 > and has made a number of contributions [0] and reviews [1].

Re: [Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Jesus Fernandez
+1 from me El mié, 19 ene 2022 a las 13:00, Volker Hilsheimer () escribió: > Hi, > > I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt > Project. > > Jimis has been working as a Software Engineer in the Qt Company since 2019 > and has made a number of contributions [0]

[Development] Nominating Dimitrios "Jimis" Apostolou as Approver

2022-01-19 Thread Volker Hilsheimer
Hi, I’d like to nominate Dimitrios Apostolou, aka Jimis, as approver in the Qt Project. Jimis has been working as a Software Engineer in the Qt Company since 2019 and has made a number of contributions [0] and reviews [1]. Most of his work happens in the build and test machinery and the

Re: [Development] Nominating Sona Kurazyan as maintainer of qt5compat

2022-01-19 Thread Andrei Golubev
+1 from me as well. While I haven't interacted with qt5compat much, I trust Sona. She also, evidently, did significant contributions to that module. Disclaimer: we used to be on the same team. -- Best Regards, Andrei From: Development on behalf of Kevin Kofler

[Development] [Announce] Qt Creator 6.0.2 released

2022-01-19 Thread List for announcements regarding Qt releases and development
We are happy to announce the release of Qt Creator 6.0.2! https://www.qt.io/blog/qt-creator-6.0.2-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

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Alexandru Croitor
> On 19. Jan 2022, at 04:01, Thiago Macieira wrote: > > 1) assume all compilers support what we need > > I propose we remove the tests for the intrinsics of each individual CPU > feature. Instead, let's just assume they all have everything up to 2016. > > The change

Re: [Development] Updating x86 SIMD support in Qt

2022-01-19 Thread Lars Knoll
Hi Thiago, I’m absolutely in favour of upping the SIMD support in Qt. Compilers support everything we need, and we should make better use of that. The main thing I’m wondering about is how much performance we gain by from a multi arch build Qt for different x86_64 architectures opposed to