[Nasm-bugs] [Bug 3392561] %ifn in a certain context allows undefined symbol, which activates its clause

noreply-nasm at gorcunov.org noreply-nasm at gorcunov.org
Wed Mar 6 08:12:35 PST 2019


--- Comment #2 from H. Peter Anvin <hpa at zytor.com> ---
Ok, seems like the real problem is that the error message gets promoted because
we encounter an error before pass 1. At the very least it should not be emitted
in the very first pass (passn == 1), perhaps not in any of the optimization
passes either (pass0 == 0).

If it happens in the stabilization pass we have a phase error, but perhaps the
best is to defer this to pass 2 and let the phase error be signalled as-is.

Ideally, we would keep track of preprocessor changes between the stabilization
and code-generation passes just like we do symbol changes; this would require
recording every preprocessor event ideally in some form that can be
resynchronized after an error.

You are receiving this mail because:
You are on the CC list for the bug.
You are watching all bug changes.

More information about the Nasm-bugs mailing list