Toms
Toms
There are compilers on decomp.me that do support C++ code but rely on file extension to determine if they should use the C++ compiler. For example, this seems to be...
 Note - edited code to add a print to see what the mismatch is with `ui.label(format!("Instruction count mismatch {} != {}", left_symbol_diff.instruction_rows.len(), right_symbol_diff.instruction_rows.len()));` [instcountissue.zip](https://github.com/user-attachments/files/19467847/instcountissue.zip) instcountissuecoff is compiled with watcom...
in this object compiler generated scalar destructor shows blank  [sdtorissue.zip](https://github.com/user-attachments/files/19467265/sdtorissue.zip)
The second reloc is shown as 0 Test case is this assembly built with MASM `ml /c /coff /Zf /Cx /Cp objdiffissue_tworelocs.asm` ``` .386P .model flat .stack 4096 assume fs:nothing...
This could be used when utilizing some utility to process a batch of reports, the utility could read the timestamp and accordingly sort reports regardless of filenames
I have assembly code that calls functions that are private to that file, in objdiff these calls show as invalid, label does exist for them in the obj however reproducible...
currently to ignore prefixes somewhat specific to my workflow i have to edit is_local_label to have const LABEL_PREFIXES: &[&str] = &[".L", "off_", "loc_", "LAB_", "$L"]; would be good if these...
By doing these hacks in src/arch/x86.rs it's possible to load a 16 bit coff and it correctly disassembles in Decoder::with_ip( change Architecture::X86 => 32, to Architecture::X86 => 16, in Architecture::X86...