[Development] Clang (trunk) no longer builds Qt applications

Simon Hausmann simon.hausmann at digia.com
Tue Oct 22 15:44:00 CEST 2013


On Tuesday 22. October 2013 15.35.24 Tobias Hunger wrote:
> On 22.10.2013 15:31, Nicolás Alvarez wrote:
> > I don't think the standard is relevant here. The C++ standard doesn't
> > and can't say anything about whether 'break' and 'continue' are allowed
> > in a statement expression inside the 'for' header, because statement
> > expressions don't exist in the standard to begin with; they are a gcc
> > extension. Clang has to reverse engineer the exact semantics from gcc
> > behavior.
> 
> So can we avoid relying on GCC extensions here?
> 
> I doubt that we can ask clang to be 100% compatible with GCC anyway and
> making that a requirement for Qt to function properly is not what we
> should aim for IMHO.

The code in question is behind "#if defined(Q_CC_GNU)", so as long as clang 
triggers that it has to be compatible with gcc's extensions.

If it turns out that this isn't possible - i.e. they choose not to be 
compatible in this case, then we need to use the slower fall-back code that 
exists.


Simon



More information about the Development mailing list