Enum handling has been improved in the data type manager when creating new enums from an existing set of enum values, - for example “define_” enums parsed from header files. Enum values will be automatically sized to fit all the values contained - in the enum. Setting the size of an Enum will check if the values will fit within the new size. In addition, “define_” values + for example define_ enums parsed from header files. Enum values will be automatically sized to fit all the values contained + in the enum. Setting the size of an Enum will check if the values will fit within the new size. In addition, define_ values created as enums with a single value are sized to the minimum size to fit the value. Parsed enums from header files are sized based on the declared size of an int from the data organization used to parse. A future version will have a setting to size all parsed enums to the smallest size that will fit all the values.
The C-Parser GUI has been refactored to remove include paths from the Options section done as –D define lines, to a new Include section. +
The C-Parser GUI has been refactored to remove include paths from the Options section done as -D define lines, to a new Include section. This should make it easier to configure paths to the include files and has the added benefit of coloring the include file entries red if they are not found within any include path. You may find creating and using a Ghidra Script instead of the GUI an easier repeatable process. There are several included examples scripts, including ones to parse AVR8 header files, and Visual Studio version 22 files.
@@ -195,8 +195,8 @@Constant Propagation now deals with constants passed as stack parameters. In addition, there are several new settings which can better - control when a constant is considered to be an address. For example, processors with small memory spaces, the setting “Require pointer param - data type,” will only create a reference if the parameter is declared with a data type that would be a pointer. This can be useful for Harvard + control when a constant is considered to be an address. For example, processors with small memory spaces, the setting Require pointer param + data type, will only create a reference if the parameter is declared with a data type that would be a pointer. This can be useful for Harvard architectures with multiple address spaces used in conjunction with the PointerTypedef to specify the address space of the pointer. Currently, once you change the parameter of a called function to be a pointer, you will need to re-run analysis to get the constants passed to the function to be turned into a reference. This will be automated in the near future.
@@ -214,15 +214,15 @@Improvements and bug fixes have been made to many processors since 10.2 to include: - AARCH64, ARM, Coldfire, HCS12 MIPS X86, PowerPC, RISCV SPARC, SuperH, TriCore, V850, Z80, 6x09, 68K, and 8051.
+AARCH64, ARM, Coldfire, HCS12 MIPS X86, PowerPC, RISCV SPARC, SuperH, TriCore, V850, Z80, 6x09, 68K, and 8051.
- Two new user-submitted processors, eBPF and BPF, add support for two variants of Berkeley Packet Filter binaries.
+Two new user-submitted processors, eBPF and BPF, add support for two variants of Berkeley Packet Filter binaries.
A user-submitted refactoring of X86 LOCK/UNLOCK decoding and semantics has been committed. There are currently some issues with the
Decompiler re-arranging code outside of the LOCK/UNLOCK which will be addressed an upcoming patch. If your analysis depends on
the LOCK/UNLOCK semantics, please be aware of the issue.
A new “leading zeroes count” operator, called lzcount, has been added to p-code, and it can now be used by SLEIGH developers
+
A new leading zeroes count operator, called lzcount, has been added to p-code, and it can now be used by SLEIGH developers
to model processor instructions. The Decompiler can simplify common code idioms using these instructions, and emulation is supported.