Ghidra1

Could you please provide some additional details: 1. Is this in relationto a multi-user shared project merge/checkin or a program Diff merge? 2. If using Diff merge does the source...

The issue may be a merge code issue which is suppose to work with equivalent addresses and not directly compare objects/addresses between two programs. I will need to check code...

The use of `!=` is correct. The error is caused by improper use of the remove method which expects a contiguous address range within a single address space. If your...

Merge works with multiple program instances which will each have their own overlay address space instances. Merge is not suppose to mix addresses and must carefully perform cross-lookups for such...

The use of auto-return-storage is only supported by dynamic storage allocation (non-custom storage) based upon the current calling convention and the return datatype. If using custom storage we rely on...

It is important that we try to get the compiler specification and allocations correct since it not only affects the forward direction (i.e., allocation when signature is known), it also...

Since this same issue also impacts how parameters are passed this needs to be addressed at the compiler spec level. The current thinking is that an optional attribute is needed...

Is this specifically StackFrame.getLocalSize() or StackFrame.getParameterSize() that you are hoping to see? These are computed based upon the defined variables that utilize the stack. There is also the potential impact...

Your original implementation is at version 1.0 while ours is 4.0. This was done for internal reasons. If you like, you can create an old language mapping/translator if this will...

@artemy has sufficient information been provided that we may close this ticket?