summaryrefslogtreecommitdiff
path: root/nasmlib
diff options
context:
space:
mode:
authorH. Peter Anvin (Intel) <hpa@zytor.com>2018-12-18 12:25:11 -0800
committerH. Peter Anvin (Intel) <hpa@zytor.com>2018-12-18 12:25:11 -0800
commit5df6ca712df59a7f83b27ebd382bfb6ee851fff8 (patch)
treed926fa961f5a91c71317ac34c2867246f8d229eb /nasmlib
parent21da8ae8e5163aa6dd2042d70a7530d7d6accab7 (diff)
downloadnasm-5df6ca712df59a7f83b27ebd382bfb6ee851fff8.tar.gz
With buffered warnings, change the handling of error passes
With buffered warnings, most warnings *must* be issued on every pass, so ERR_PASS1 is simply wrong in most cases. ERR_PASS1 now means "force this warning to be output even in pass_first(). This is to be used for the case where the warning is only executed in pass_first() code; this is highly discouraged as it means the warnings will not appear in the list file and subsequent passes may make the warning suddenly vanish. ERR_PASS2 just as before suppresses an error or warning unless we are in pass_final(). Signed-off-by: H. Peter Anvin (Intel) <hpa@zytor.com>
Diffstat (limited to 'nasmlib')
-rw-r--r--nasmlib/readnum.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/nasmlib/readnum.c b/nasmlib/readnum.c
index 4e73c1a1..3ed6b3f2 100644
--- a/nasmlib/readnum.c
+++ b/nasmlib/readnum.c
@@ -169,7 +169,7 @@ int64_t readnum(const char *str, bool *error)
*! covers warnings about numeric constants which
*! don't fit in 64 bits.
*/
- nasm_error(ERR_WARNING | ERR_PASS1 | WARN_NUMBER_OVERFLOW,
+ nasm_error(ERR_WARNING | WARN_NUMBER_OVERFLOW,
"numeric constant %s does not fit in 64 bits",
str);
}