Better warnings for out-of-range values

Issue better warnings for out-of-range values.  This is not yet
complete.

In particular, note we may have out-of-range for values that end up
being subject to optimization.  That is because the optimization takes
place on the *truncated* value, not the pre-truncated value.

Signed-off-by: H. Peter Anvin <hpa@zytor.com>

1 files changed, 2 insertions, 1 deletions

diff --git a/nasm.c b/nasm.c
index 7bdc96e2..76d1eee0 100644
--- a/nasm.c
+++ b/nasm.c
@@ -1888,7 +1888,8 @@ static bool is_suppressed_warning(int severity)
 	(((severity & ERR_WARN_MASK) != 0 &&
 	  !warning_on[(severity & ERR_WARN_MASK) >> ERR_WARN_SHR]) ||
 	 /* See if it's a pass-one only warning and we're not in pass one. */
-	 ((severity & ERR_PASS1) && pass0 != 1));
+	 ((severity & ERR_PASS1) && pass0 != 1) ||
+	 ((severity & ERR_PASS2) && pass0 != 2));
 }
 
 /**