Re: [Development] INTEGRITY help needed: IPC & QT_CONFIG weirdness

2022-11-05 Thread Thiago Macieira
On Saturday, 5 November 2022 11:35:15 PDT Thiago Macieira wrote: > TL;DR: Please propose a patch by end of week to fix the INTEGRITY error from > https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1679359812 Ok, now I need QNX help from build https://testresults.qt.io/coin/integration/qt/q

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Thiago Macieira
On Saturday, 5 November 2022 12:21:29 PDT Alexandru Croitor via Development wrote: > and FEATURE_systemsemaphore will be disabled on integrity due to its > condition in configure.cmake as shown below. > > CONDITION ( NOT INTEGRITY AND NOT VXWORKS AND NOT rtems ) AND ( ANDROID OR > WIN32 OR TEST_s

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Alexandru Croitor via Development
Hi, The feature is marked in configure.cmake as PRIVATE only. Try explicitly including one or both of #include #include Note that in src/corelib/ipc/qsystemsemaphore_p.h there is #if QT_CONFIG(systemsemaphore) #include "qcoreapplication.h" #include "qtipccommon_p.h" #include "private/qtcore-

[Development] INTEGRITY help needed: IPC & QT_CONFIG weirdness

2022-11-05 Thread Thiago Macieira
TL;DR: Please propose a patch by end of week to fix the INTEGRITY error from https://testresults.qt.io/coin/integration/qt/qtbase/tasks/1679359812 Longer: I have a 34-patch series refactoring a lot of the IPC mechanisms in Qt, in particular QSharedMemory and QSystemSemaphore. It starts here: ht

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Thiago Macieira
On Saturday, 5 November 2022 10:08:55 PDT Allan Sandfeld Jensen wrote: > Sure. If we can, make it a stand in for std::float16_t until we can rely on > that. https://codereview.qt-project.org/c/qt/qtbase/+/305792 https://codereview.qt-project.org/c/qt/qtbase/+/441813 https://codereview.qt-project.o

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Allan Sandfeld Jensen
On Samstag, 5. November 2022 16:56:27 CET Thiago Macieira wrote: > On Saturday, 5 November 2022 01:16:36 PDT Marc Mutz via Development wrote: > > Done. Also for qfloat16. > > qfloat16 needs some TLC to adapt to P1467. I have the patches for that and > have tested that they work in a processor emul

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Thiago Macieira
On Saturday, 5 November 2022 01:16:36 PDT Marc Mutz via Development wrote: > Done. Also for qfloat16. qfloat16 needs some TLC to adapt to P1467. I have the patches for that and have tested that they work in a processor emulator[1]. Is that acceptable? [1] https://www.intel.com/content/www/us/en

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Marc Mutz via Development
On 05.11.22 08:24, Marc Mutz via Development wrote: > There's alsohttps://bugreports.qt.io/browse/QTBUG-94266 > > I'll clone that for QFixed. Done. Also for qfloat16. I've also updated the epic (https://bugreports.qt.io/browse/QTBUG-104180) with information regarding wg21.link/P2484 which aims

Re: [Development] C++20 structural types (was: C++20 @ Qt)

2022-11-05 Thread Marc Mutz via Development
Hi Thiago, On 04.11.22 16:49, Thiago Macieira wrote: > I've just hit this: should we make some of our very simple types even simpler > so they're structural types[1] and thus can be passed as template parameters? > > For example, QFlags. I've just tried it and I get: > > error: ‘QFlags’ is not a