On Wed, May 31, 2017 at 5:49 PM, Ian Romanick wrote:
> On 05/31/2017 06:09 AM, Emil Velikov wrote:
>> On 31 May 2017 at 01:55, Ian Romanick wrote:
>>> I don't understand these warnings, and I have even less understanding of
>>> how "using" fixes them. For example...
>>>
>>> On 05/30/2017 01:47 P
On 05/31/2017 06:09 AM, Emil Velikov wrote:
> On 31 May 2017 at 01:55, Ian Romanick wrote:
>> I don't understand these warnings, and I have even less understanding of
>> how "using" fixes them. For example...
>>
>> On 05/30/2017 01:47 PM, Rob Herring wrote:
>>> clang gives warnings about overload
On 31 May 2017 at 01:55, Ian Romanick wrote:
> I don't understand these warnings, and I have even less understanding of
> how "using" fixes them. For example...
>
> On 05/30/2017 01:47 PM, Rob Herring wrote:
>> clang gives warnings about overloaded virtual functions:
>>
>> src/compiler/glsl/linke
I'm not sure if it's a good idea to hide these warnings, I think there
is an underlying design issue over there.
On 05/30/2017 10:47 PM, Rob Herring wrote:
clang gives warnings about overloaded virtual functions:
src/compiler/glsl/linker.cpp:244:30: warning: '(anonymous
namespace)::array_resi
I don't understand these warnings, and I have even less understanding of
how "using" fixes them. For example...
On 05/30/2017 01:47 PM, Rob Herring wrote:
> clang gives warnings about overloaded virtual functions:
>
> src/compiler/glsl/linker.cpp:244:30: warning: '(anonymous
> namespace)::array
clang gives warnings about overloaded virtual functions:
src/compiler/glsl/linker.cpp:244:30: warning: '(anonymous
namespace)::array_resize_visitor::visit' hides overloaded virtual function
[-Woverloaded-virtual]
virtual ir_visitor_status visit(ir_variable *var)
^
