On Fri, Jun 19, 2015 at 1:19 PM, Chih-Wei Huang wrote:
> 2015-06-20 1:01 GMT+08:00 Ilia Mirkin :
>> Wouldn't it be simpler to just have
>>
>> codegen/unordered_set.h
>>
>> which in turn has all the odd logic? I'm definitely a tad unhappy
>> about adding "using" in a header, but if the using goes i
2015-06-20 1:01 GMT+08:00 Ilia Mirkin :
> Wouldn't it be simpler to just have
>
> codegen/unordered_set.h
>
> which in turn has all the odd logic? I'm definitely a tad unhappy
> about adding "using" in a header, but if the using goes inside the
> nv50_ir namespace, I'm less weirded out by it. And t
Wouldn't it be simpler to just have
codegen/unordered_set.h
which in turn has all the odd logic? I'm definitely a tad unhappy
about adding "using" in a header, but if the using goes inside the
nv50_ir namespace, I'm less weirded out by it. And then effectively
all 3 become nv50_ir::unordered_set,
If build with C++11 standard, use std::unordered_set.
Otherwise if build on old Android version with stlport,
use std::tr1::unordered_set with a wrapper class.
Otherwise use std::tr1::unordered_set.
Signed-off-by: Chih-Wei Huang
---
Android.common.mk | 1 +
sr
