Re: [Development] Houston, qint128 has a problem

2024-07-09 Thread Karl Semich
Comment from peanut gallery, > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40856 > This code should produce the same results with -std=g++11 and -std=c++11 > I will not object to patches tweaking the condition and positively reviewed > by fellow maintainers. It sounds like the GCC maintainers

[Development] Proposing QUIP-23: Qt-Security header in source code files

2024-07-09 Thread Dimitrios Apostolou via Development
Hello list, on behalf of the Qt Company, I would like to propose a new single-line comment header for the Qt source code. The syntax is: // Qt-Security score:N reason:some-reason [labels:label1,label2] The idea is to mark files with code where bugs are more likely to cause security issues

Re: [Development] Houston, qint128 has a problem

2024-07-09 Thread Thiago Macieira
On Tuesday 9 July 2024 03:33:16 GMT-7 Marc Mutz via Development wrote: > We should really try to fix this before 6.8.0 (LTS). I won't have time for QDataStream and especially QTextStream & QDebug, which are required for QMetaType. -- Thiago Macieira - thiago.macieira (AT) intel.com Principal

Re: [Development] Houston, qint128 has a problem

2024-07-09 Thread Marc Mutz via Development
We should really try to fix this before 6.8.0 (LTS). On 09.12.23 18:38, Thiago Macieira wrote: > On Friday, 8 December 2023 18:51:19 PST Marc Mutz via Development wrote: >> I think we need to mandate that if you want qint128 support, then you >> must compile with gnu++NN, which is actually the def