[virglrenderer-devel] [PATCH 00/16] Fix warnings in gallium/auxiliary/*
Gert Wollny
gert.wollny at collabora.com
Tue Jun 5 12:04:00 UTC 2018
Am Dienstag, den 05.06.2018, 08:32 +0200 schrieb Gert Wollny:
> Am Dienstag, den 05.06.2018, 14:42 +1000 schrieb Dave Airlie:
> > On 5 June 2018 at 01:53, Gurchetan Singh <gurchetansingh at chromium.o
> > rg
> > > wrote:
> > > I've always wondered why building Mesa (and Gallium) always
> > > spewed
> > > out so many warnings. Would it be possible to fix this in
> > > upstream
> > > Mesa, and have the changes trickle down to here when update our
> > > Gallium code? I know we've forked Gallium, but is the fork hard
> > > enough that this would not work (we essentially support a few
> > > more
> > > outdated TGSI opcodes [TGSI_OPCODE_SCS etc.])?
> >
> > I'm also worried about this diverging us from Mesa more than we'd
> > want to, syncing is already getting difficult but I'm not sure I'd
> > too add too many more obstacles.
>
> Fair enough.
>
> > It might be nice to try and approach mesa with these fixes first.
>
> I'll submit the adjusted patch set to mesa, there is quite a number
> of developers willing to review warning-fixing patches.
Sent to mesa if someone wants to review:
https://patchwork.freedesktop.org/series/44269/
Best,
Gert
More information about the virglrenderer-devel
mailing list