[Mesa-dev] swr forces c++11 for whole compilation

Jose Fonseca jfonseca at vmware.com
Wed Apr 13 13:06:57 UTC 2016


On 13/04/16 13:48, Jose Fonseca wrote:
> On 13/04/16 11:43, Ilia Mirkin wrote:
>> Hi Tim,
>>
>> It seems like building swr forces c++11 mode for the whole build, even
>> other drivers being built that aren't necessarily ready for it.
>> Unfortunately c++11 isn't backwards compatible with c++03, so the switch
>> can't be made unilaterally. Could you have a look at why this is
>> happening?
>>
>> An example of something that does this properly is clover, which also
>> requires c++11 to be built.
>>
>> Thanks,
>>
>>    -ilia
>>
>
> Ilia,
>
> Even before SWR was merged and today's isinf fix was commited,
> nv50_ir_ra.cpp already has code to make it portable for C++11 (see below).
>
> I honestly don't understand what you're trying to achieve with this
> thread...
>
> Are you seriously plan to require C++03 to build nouveau?  It would be
> insane try to do that once GCC 6 is widely available.
>
> Rather than see you swimming upstream, I much rather see you helping me
> helping you to keep nouveau C++11 portable...
>
> Jose
>

FYI, llvm also forces -std=c++11:

$ llvm-config --cxxflags
-I/usr/lib/llvm-3.6/include  -DNDEBUG -D_GNU_SOURCE 
-D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -g 
-O2 -fomit-frame-pointer -std=c++11 -fvisibility-inlines-hidden 
-fno-exceptions -fPIC -ffunction-sections -fdata-sections -Wcast-qual

and AFAICS configure.ac does not strip it.

Jose


More information about the mesa-dev mailing list