More conservative field resolution in MLIL/HLIL for bitfields

Assessment

This issue has not been assessed yet.

Description

What is the feature you'd like to have?
The new bitfield support in structures is awesome, but until bitfield resolution is added to MLIL/HLIL (https://github.com/Vector35/binaryninja-api/issues/7533), I think there should be at least an option to disable displaying bitfield accessors on MLIL/HLIL.

Is your feature request related to a problem?
For example when using the SVD loader plugin, a bunch of registers will include bitfields, and HLIL will always defaults to the first bitfield. This is my opinion produces misleading output and makes you think the code is dealing with a bitfield when it is really not.

Here are two examples:

Are any alternative solutions acceptable?
I see two possible ways:

• Add an option to enable/disable using bitfields in the MLIL/HLIL views
• In the SVD plugin, add an option to not create bitfields in the structures

The second option is not very good as the problem will persist for any structure using bitfields which wasn't created by the SVD plugin.

Additional Information:
One clear example where printing bitfields will be misleading is working with an MCP server. Any LLM accessing the MLIL/HLIL view produced by binary ninja will think that is bitfield being accessed and totally mess up....

Contributor guide

No contributing guide indexed for this repository

First steps

1. Read the whole issue, then the project's contributing guide.
2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
3. Fork the repository and make your change on a branch.
4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

• `Function::IsVariableUserDefinded` is misspelt in the C++ API Open

  Difficulty 1/5 1-3 hours Newbie friendliness 88/100

  Vector35/binaryninja-api#8540 · Opened Sep 10, 2026

• MSP430: conditional_jump! macro initialises new_true to true, emitting a spurious jump Open

  Difficulty 2/5 1-3 hours Newbie friendliness 88/100

  Vector35/binaryninja-api#8516 · Opened Sep 3, 2026

• MSP430: Sub lifts operands in reverse order (inconsistent with Cmp) Open

  Difficulty 1/5 Under an hour Newbie friendliness 92/100

  Vector35/binaryninja-api#8503 · Opened Sep 1, 2026

• normalize time logs from WARP Open

  Difficulty 1/5 Under an hour Newbie friendliness 88/100

  Vector35/binaryninja-api#8446 · Opened Aug 20, 2026

• component data variable notifications raise AttributeError Open

  Difficulty 1/5 Under an hour Newbie friendliness 88/100

  Vector35/binaryninja-api#8444 · Opened Aug 20, 2026

All issues in Vector35/binaryninja-api

Similar issues

• Eval bug: SIGSEGV in token-counting routes when the request arrives while the server is sleeping (stale vocab/mctx captured before the wake barrier) Open

  Difficulty 2/5 1-3 hours Newbie friendliness 86/100

  ggml-org/llama.cpp#29188 · Opened Sep 20, 2026

• Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open

  Difficulty 2/5 1-3 hours Newbie friendliness 78/100

  gazebosim/gz-sensors#662 · 1 comment · Opened Sep 20, 2026

• Aligned columns on the serial monitor while keeping CSV on the SD card Open
  enhancement

  Difficulty 2/5 1-3 hours Newbie friendliness 76/100

  NorthernWidget/Margay_Library#31 · Opened Sep 20, 2026

• v1 manifest list: existing_files_count is the table-wide total-data-files Open
  comp-datalake

  Difficulty 2/5 1-3 hours Newbie friendliness 88/100

  ClickHouse/ClickHouse#121222 · Opened Sep 20, 2026

• Case collision between `Canvas` and `canvas` test directories causes platform-dependent source hashes Open

  Difficulty 2/5 1-3 hours Newbie friendliness 68/100

  LadybirdBrowser/ladybird#12123 · Opened Sep 20, 2026

More C++ issues