| Age | Commit message (Collapse) | Author |
|---|
|
New special-name and type demangling:
- GTt/GTn: GCC transaction clone symbols
- TH/TW: TLS init and wrapper functions
- Tc: covariant return thunks with dual call-offset parsing
- Demangle _block_invoke symbols (Clang/Apple block invocations)
- Intel Vector Function ABI (_ZGV) with ISA, mask, vlen, parameter
kind parsing; z/Z guard variable disambiguation
- Vendor-extended type (U <source-name>) for Objective-C block pointers
- Lowercase vendor type (u <source-name>) for __remove_cvref etc.
- GR <object name> reference temporary demangling
- macOS $tlv$init thread-local variable initializer suffix
- Fix typeinfo rendering to avoid duplicated name in output
New operator and constructor support:
- ABI tag (B <source-name>) consumption in DemangleUnqualifiedName,
DemangleNestedName, and DemangleFunction
- CI1/CI2 inheriting constructors with m_lastName save/restore
- M data-member-prefix in DemangleNestedName for lambdas in
data member initializers
- operator<=> (spaceship) in GetOperator and DemangleUnqualifiedName
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
|
Replace the TypeBuilder-based demangling path with a lightweight
DemangledTypeNode representation that defers type object construction
until the symbol is fully parsed. This avoids repeated heap allocation
and ref-count churn during recursive descent.
Key changes:
- Add DemangledTypeNode / demangled_type_node.{h,cpp}: a compact IR
that mirrors the type grammar without allocating BN Type objects
- Use a thread_local demangler instance to amortize vector allocations
across calls
- Also commonize some of the demangled string length calculations.
Result: ~3x throughput improvement on a 180K-symbol corpus with
97.7% success rate (matching the previous implementation).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
|
|
|
Loggers are not owned by a specific thread and many are used by multiple threads. The indenting APIs could not be made to be thread safe in any way as they exist, so they have been removed. The data races caused by the indenting APIs are actually an important stability issue that could cause the indentation level to go out of bounds and crash the product.
If you were using the indentation APIs, you will need to rewrite the usage to manually manage the indentation level in a thread safe way.
|
|
message
|
|
This ensures that CMake detects when files that match the glob are added
or removed.
|
|
Also update minimum CMake version.
|
|
cause bugs and also issues with C++20
|
|
Fixes https://github.com/Vector35/binaryninja-api/issues/6902 however we still need to figure out what we want to do about the type info names being invalid. There really is not a good way to tell without saying all type info names _must_ be mangled.
|
|
|
|
|
|
Fixes #6261
|
|
|
|
Turns out, this is a rather hot path on initial binary loading (>50% runtime), and trying to pipe it all through the FFI makes it really slow. Like 100% slower. Ouch. Now, the demangler plugins are written with a bunch of #ifdef macros to allow for building both as a plugin and directly into the core. There is no functionality change here apart from regaining the lost performance.
|
|
|
|
|
|
Closes #467
|
