diff options
author | wm4 <wm4@nowhere> | 2019-07-06 23:54:50 +0200 |
---|---|---|
committer | wm4 <wm4@nowhere> | 2019-09-19 20:37:05 +0200 |
commit | 9e1945d3074dbde9e730ae8be8eea7b86e9b7112 (patch) | |
tree | 00e7b6743a612b60b2bedc8dd951caecae5ce775 | |
parent | 11027e99f246371837f9d866936066282da11b9f (diff) | |
download | mpv-9e1945d3074dbde9e730ae8be8eea7b86e9b7112.tar.bz2 mpv-9e1945d3074dbde9e730ae8be8eea7b86e9b7112.tar.xz |
win_state: silence a valgrind warning
m_geometry_apply() will read and modify the dummy variable. It's not
actually used for anything, but valgrind will still warn against
uninitialized data. I'm not sure whether this was UB, but in any case
it's annoying when running valgrind.
-rw-r--r-- | video/out/win_state.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/video/out/win_state.c b/video/out/win_state.c index f9fb0cab52..96857160cf 100644 --- a/video/out/win_state.c +++ b/video/out/win_state.c @@ -42,7 +42,7 @@ static void apply_autofit(int *w, int *h, int scr_w, int scr_h, if (!geo->wh_valid) return; - int dummy; + int dummy = 0; int n_w = *w, n_h = *h; m_geometry_apply(&dummy, &dummy, &n_w, &n_h, scr_w, scr_h, geo); |