[Nasm-bugs] [Bug 3392662] nasm-2.15rc1 breaks firefox build (possibly related to 3392652?)

[noreply-nasm at dev.nasm.us]

https://bugzilla.nasm.us/show_bug.cgi?id=3392662

Chang S. Bae <chang.seok.bae at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|OPEN                        |CONFIRMED

--- Comment #1 from Chang S. Bae <chang.seok.bae at intel.com> ---
I just stepped back tagging 2.15rc1 while still considered to be the candidate
at the moment. 

Right, BR3392652 was raising hang issue when building some source from Firefox.
Although resolved, we still have such leftovers here. I suspect the regression
came from some past changes, not from recent updates.

>From bisected, this commit began to emit a bunch of errors and warnings, which
now reduced to a few. The commit involves lots of changes, so it takes one's
time to factor things out before finding a solution.

commit 8b262474424c0f6912b22bbf7452f26bfa4d1235 HEAD (HEAD -> tmp)
Author: H. Peter Anvin <hpa at zytor.com>
Date:   Tue Feb 26 14:00:54 2019 -0800

    preproc: add %i... variants, evaluated macro parameters, cleanups

    All directives which create single-line macros now have %i... variants
    to define case-insensitive versions. Case insensitive rather sucks,
    but at least this way it is consistent.

    Single-line macro parameters can now be evaluated as a number, as done
    by %assign. To do so, declare a parameter starting with =, for
    example:

    %define foo(x,=y) mov [x],macro_array_y

    ... would evaluate y as a number but leave x as a string.

    NOTE: it would arguably be better to have this as a per-instance
    basis, but it is easily handled by having a secondary macro called
    with the same argument twice.

    Finally, add a more consistent method for defining "magic" macros,
    which need to be evaluated at runtime. For now, it is only used by the
    special macros __FILE__, __LINE__, __BITS__, __PTR__, and __PASS__.

    __PTR__ is a new macro which evaluates to word, dword or qword
    matching the value of __BITS__.

    The magic macro framework, however, provides a natural hook for a
    future plug-in infrastructure to hook into a scripting language.

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

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