From 8d965a1bfb3782343a03cff44977f11bb920f0b1 Mon Sep 17 00:00:00 2001
From: wm4 <wm4@nowhere>
Date: Fri, 13 Mar 2020 16:49:39 +0100
Subject: options: change how option range min/max is handled

Before this commit, option declarations used M_OPT_MIN/M_OPT_MAX (and
some other identifiers based on these) to signal whether an option had
min/max values. Remove these flags, and make it use a range implicitly
on the condition if min<max is true.

This requires care in all cases when only M_OPT_MIN or M_OPT_MAX were
set (instead of both). Generally, the commit replaces all these
instances with using DBL_MAX/DBL_MIN for the "unset" part of the range.

This also happens to fix some cases where you could pass over-large
values to integer options, which were silently truncated, but now cause
an error.

This commit has some higher potential for regressions.
---
 video/decode/vd_lavc.c | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'video/decode')

diff --git a/video/decode/vd_lavc.c b/video/decode/vd_lavc.c
index b41c4c48c6..76f2b46e3e 100644
--- a/video/decode/vd_lavc.c
+++ b/video/decode/vd_lavc.c
@@ -15,6 +15,7 @@
  * License along with mpv.  If not, see <http://www.gnu.org/licenses/>.
  */
 
+#include <float.h>
 #include <stdio.h>
 #include <stdlib.h>
 #include <pthread.h>
@@ -110,7 +111,7 @@ const struct m_sub_options vd_lavc_conf = {
         OPT_DISCARD("vd-lavc-skipidct", skip_idct, 0),
         OPT_DISCARD("vd-lavc-skipframe", skip_frame, 0),
         OPT_DISCARD("vd-lavc-framedrop", framedrop, 0),
-        OPT_INT("vd-lavc-threads", threads, M_OPT_MIN, .min = 0),
+        OPT_INT("vd-lavc-threads", threads, 0, .min = 0, .max = DBL_MAX),
         OPT_FLAG("vd-lavc-bitexact", bitexact, 0),
         OPT_FLAG("vd-lavc-assume-old-x264", old_x264, 0),
         OPT_FLAG("vd-lavc-check-hw-profile", check_hw_profile, 0),
-- 
cgit v1.2.3