aboutsummaryrefslogtreecommitdiffstats
path: root/src/gallium/drivers/zink/zink_framebuffer.h
diff options
context:
space:
mode:
authorEric Anholt <[email protected]>2019-12-16 21:23:02 -0800
committerEric Anholt <[email protected]>2020-01-28 12:31:07 -0800
commitf6e59911e52161527d1d416e6807b0bc4d639011 (patch)
tree17ce0dfdc1ed434185864d22e6681c4cf404543b /src/gallium/drivers/zink/zink_framebuffer.h
parent527a8c345bf2b011c867f1c4d0356d0f0f3c647d (diff)
ci: Enable -Werror on the meson-i386 build.
I find warnings to be very disruptive to my workflow (using emacs's "go to next error" feature), and I periodically have to go clean up other people's drivers to get back to finding my own warnings in the noise. I know I'm not the only one doing something like this. We don't want to enable -Werror by default in builds, since it means that end users will have builds spuriously fail based on what compiler version and opt flags they have compared to what the devs are using. However, it is quite easy to have CI ensure that we at least don't introduce warnings on the compiler version that it uses. For now I've just enabled it on meson-i386 to cover a bunch of Mesa core and get us started on ratcheting up warnings-cleanliness in the tree, without me having to fix up all the drivers at once. Reviewed-by: Daniel Stone <[email protected]> Reviewed-by: Kristian H. Kristensen <[email protected]> Reviewed-by: Alyssa Rosenzweig <[email protected]> Reviewed-by: Eric Engestrom <[email protected]> Tested-by: Marge Bot <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3539> Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3539>
Diffstat (limited to 'src/gallium/drivers/zink/zink_framebuffer.h')
0 files changed, 0 insertions, 0 deletions