Skip to content

v0.7.0

Choose a tag to compare

@github-actions github-actions released this 12 Nov 13:28
3eeeed8

Fixed

  • The IDA, Binary Ninja and Ghidra scripts read Mach-O names without their leading
    underscore.
    Mach-O puts one underscore in front of every symbol, and the tools keep
    it, so Nim's _area__mymod_u10 came out as mymod._area, JNI's _Java_... was not
    read, and Free Pascal, Ada and GCC 2 names were read with the underscore as part of the
    name. On a Mach-O file a name is now read without it, except where C++, Swift, Rust, D
    or Objective-C reads it as it stands (__Z, _$s, __D, ...), which those schemes do
    already and which keeps Apple's C++ rules. demangle_labels.Options has a
    leading_underscore field for it, and each script a LEADING_UNDERSCORE setting that
    overrides the file type. Checked in IDA 9.5, Binary Ninja 6.0 and Ghidra 12.2 on a
    Mach-O arm64 dylib.
  • The Binary Ninja plugin leaves alone an address holding several user symbols.
    Binary Ninja's DWARF import defines a user symbol for each function the linker
    discarded, all at the image base beside __elf_header. With
    ONLY_LEFT_MANGLED = False on a Rust program the plugin relabelled one of them, which
    dropped __elf_header, and Undo did not bring it back. Such an address is now skipped
    and counted in the summary line. Found running the plugin live in Binary Ninja 6.0 on
    Linux; the IDA script was run live in IDA 9.5, through idalib and idat -S, with
    nothing to fix. Both were then run from their windows, the Plugins menu of Binary Ninja
    6.0.10905 and File > Script file in IDA 9.5, with Cancel, Undo and Redo behaving as
    documented.
  • An MSVC name holding _$$_ or a / is no longer read as Free Pascal or Go.
    ?A_$$_B@@3HA read as a Free Pascal routine B@@3HA in a unit ?A, where it is
    MSVC's int A_$$_B, and an MSVC string literal with a / in it was claimed by Go and
    left as it was. Neither scheme writes a name opening ?.
  • Swift follows upstream's renames (weekly drift report #70). The called-once
    function conventions are @once (XO) and @callable(once) (XOo), where they were
    @called(exactlyOnce) and @called(atMostOnce), and Twa after a type metadata
    accessor reads as back deployment copy of type metadata accessor for ..., where it
    was refused. The Swift reference build moves to swiftlang/swift main @ 4f010677
    (2026-11-12), which reproduces the corpora: 531 / 531, 217 / 217, 71 / 71. Rust's
    #[rustc_splat] is not followed yet: it is on rustc-demangle's main only, and the
    released 0.1.28 that the reference builds still prints #[splat].
  • MSVC: a conversion operator used as an alias template's argument is declined
    cleanly.
    ?f@@YAXV?$A@$$Y?$?BH@@@@V?$A@$$Y?$?BH@@@@@Z failed on an internal
    ValueError, because the placeholder for a conversion operator's name and the mark
    for a function type's calling convention shared a delimiter. They are now distinct,
    and the name is refused as llvm-undname refuses it.
  • Swift reads a propagated @differentiable function argument. A function
    signature specialization parameter a (...Tf1na_n) carries the original function
    and its JVP and VJP, each as a name and a type, and prints as [Differentiable Function Propagated, Components : [...]]; it was refused. That was the last vector of
    the drift report this library did not read. swift-upstream.txt now holds it and the
    three Twa rows: 535 / 535 against the reference build at 4f010677.
  • Playground navigation, presets, and cards share centered page gutters and a bounded
    content width. Inner padding, control sizing, and responsive option rows stay aligned
    on desktop, narrow screens, and with enlarged text; overflow is contained locally.
  • Release recovery resumes publishing when a tag and release already exist. Active
    or successful publishing runs are preserved; failed runs retry only failed jobs.
  • Playground theme settings no longer prevent startup when browser storage is blocked.
    The theme toggle follows the system preference until the user selects a theme.
  • Automatic and manual release runs require successful push CI for the commit being tagged.

Added

  • Playground batch results preserve line order and blank lines, show individual errors,
    cache duplicate symbols, and support copying or downloading the selected output view.
  • Share links restore batch mode and validate options, with a size limit and explicit
    clipboard feedback. Result states distinguish unrecognized, invalid, and unchanged
    symbols; keyboard focus and live announcements cover batch controls and results.
  • A release-preparation command updates package and citation versions, release notes,
    and comparison links together, with metadata checks and rollback on failure.
  • Browser checks for theme persistence, keyboard shortcuts, and stalled-worker recovery.
  • IDA Pro, Binary Ninja and Ghidra scripts that label the symbols each tool leaves
    mangled, in integrations/, with a "Disassembler integrations" page. They stay out of
    the wheel.
  • benchmarks/compare.py and a "Comparison with other demanglers" page that measure this
    package against LLVM's demangler, cpp-demangle, itanium_demangler and the c++filt
    tools on the same names.
  • The weekly upstream drift job also reads every checked-in corpus with the newest LLVM,
    through llvm-demangle-fxti pinned by hash, in a job that holds no token
    (tools/llvm_oracle.py; tools/upstream_drift.py --source llvm-*, --llvm-version,
    --require-llvm and --no-llvm).

Changed

  • An MSVC name nested deep enough to reach Python's own recursion limit before
    max_depth can now be read, where 0.6.0 reported LimitExceeded. max_depth itself is
    unchanged.

Performance

  • MSVC names read about 7% faster cold, Swift names about 5% and Delphi names about
    12%. Go, Nim and Free Pascal are asked about a name before these schemes, and the
    $, __ and / they look for are in most such names. Nim and Free Pascal names
    open with a letter or _, which both now declare as their first characters, and Go's
    detect turns away a name opening ? or $ before looking for a path: no import
    path holds either, and Go's own $ constants were never claimed. Output over every
    corpus is unchanged.
  • Swift names read about 1.3 times as fast cold: identifiers are split into words only
    when a substitution needs them, and the commonest parser and printer steps make about
    40% fewer calls.
  • Template-heavy MSVC names read about 1.5 times as fast cold: each template
    instantiation is read once per name, and the control-character scan runs once.

Install with python -m pip install --upgrade demangle.

See the changelog for details.