On Wednesday 28 October 2015 13:28:39 Rafael Roquetto wrote: > Hi James, > > On Wed, Oct 28, 2015 at 02:10:02PM +0000, James McDonnell wrote: > > Fixes to 6.6.0 are...unlikely. But if you let me know what I need to > > take/do to re-produce the problem I can try to help out. Is it just this > > particular change or do I need to take all the changes in the > > 5.7-c++11-atomics topic? > > You can just take this particular change and try to build atomicfptr.cpp > manually -> this should reproduce the problem. > > (i.e. qcc -Vgcc_ntoarmv7le -o atomicfptr atomicfptr.cpp)
Plus the tests at tests/auto/corelib/thread/qatomicinteger and the atomic64.cpp config test. We may make the atomic64.cpp functionality mandatory in Qt 5.8. These will make sure other integral types are supported properly, like char16_t. Our tests don't check, but please verify whether pointer-to-members and volatile combinations work too. It would be better if DW could be fixed to support constexpr, so neither of the patches I prepared will be necessary. That is, force Q_COMPILER_CONSTEXPR to be defined in Qt dev branch and make sure at least qtbase compiles. Since that will most likely require more invasive changes to DW, we should settle for <atomic> being fixed for function pointers. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
