[Development] Using Qt 5 with C++11/Clang 3.1?
thiago.macieira at intel.com
Sat Jul 7 11:18:30 CEST 2012
On sábado, 7 de julho de 2012 10.57.01, Thiago Macieira wrote:
> On sábado, 7 de julho de 2012 09.36.55, Olivier Goffart wrote:
> > On Saturday 07 July 2012 07:33:56 Thiago Macieira wrote:
> > > On sábado, 7 de julho de 2012 02.12.42, Olivier Goffart wrote:
> > > > Anyway, if we want to support that version of clang, this still need
> > > > to
> > > > be
> > > > worked around, so I suggest that the problematic code should be
> > > > #ifdef'd
> > > > out for the 'broken' versions of clang.
> > >
> > > We also need to know which version fixes the bug so we can apply a
> > > correct
> > > version fix. And the Apple clang version and how to figure out when it
> > > is
> > > Apple clang.
> > >
> > > For now, I'd say we blacklist constexpr in Clang.
> > This has nothing to do with constexpr
> > It is the aggregate initialisation that has a small bug.
> I understand that. But the constructors only exist because we have
> constexpr. If we didn't have it, we wouldn't have added the constructors
> which would have left them as PODs.
But we can also add Q_COMPILER_UNIFORM_INITIALIZATION and blacklist that.
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 190 bytes
Desc: This is a digitally signed message part.
Url : http://lists.qt-project.org/pipermail/development/attachments/20120707/5d661fc1/attachment.bin
More information about the Development