IEStatement

This instruction has been identified as being part of an epilogue stub.

A routine's epilogue is a small instruction stub responsible for restoring registers previously saved by the prologue as well as freeing space that may have been allocated on the stack.

This instruction has been identified as being part of a prologue stub.

A routine's prologue is a small instruction stub responsible for saving registers that need to be preserved as well as allocating some space on the stack.

Statement having this flag cannot be propagated, i.e. they cannot be the source (replacement) expression in substituted expressions.

Note: even in aggressive mode, this flag is NOT ignored.

In the example below, r0 in instruction A will not be propagated to B.

 A) r0 = r1      <---- flagged
 ...
 B) r4 = .... + r0 + ...
 

Statement having this flag cannot be the recipient of substituted expressions propagated by an expression optimizer.

Note: even in aggressive mode, this flag is NOT ignored.

In the example below, r0 in instruction A could be (under conditions) substituted in instruction B. However, if instruction B has FLAG_OPT_BLOCK_SUBSTITUTIONS set, that candidate substitution will be prevented, regardless of other factors.

 A) r0 = r1
 ...
 B) r4 = .... + r0 + ...      <---- flagged
 

In the example below, r0 of A can be propagated to B (with A ending up discarded), even though A is flagged.

 A) r0 = r1                   <---- flagged
 ...
 B) r4 = .... + r0 + ...
 

Add another native instruction address mapping to this IR statement.

Add a collection of native instructions addresses mapping to this IR statement.

Perform a shallow collection of the sub-expressions of this statement. All collected expressions are directly rooted in this IRE (i.e. their parent is this IR expression).

Perform a shallow collection of the sub-expressions of this expression. All collected expressions are directly rooted in this IRE (i.e. their parent is this IR expression).

This method appends to the provided sink (existing elements are not cleared). The current element (this) is not appended; only the sub-expressions are considered.

Perform a shallow collection of the first-level expressions used by this statement. Invoking this method is not the same as calling collectSubExpressions(sink, true)! This method examines top-level defined (written) expressions that are EMem; the memory reference of those EMems are returned. Therefore, not all values returned by this method are directly rooted in this IRE. It is for that reasons that this method returns a collection of tuples (parent, expression) instead of a simple collection of expressions.

Copy (add) the native addresses of the instruction to this statement's mapping. Watch out! The current statement's mapping is not reset before copying.

Copy over the generic statement properties of the source statement onto this statement. Only generic (common) properties should be ported. The context is not copied over. Some properties are overwritten, others are completed (augmented).

Same as #equals(Object) with the possibility to exclude some properties from the comparison.

Same as #equals(Object) with the possibility to exclude some properties from the comparison.

Generate the C abstract syntax tree portion for this expression.

Get the decompiled routine context that owns this statement.

A variant of getDefUse(java.util.List, java.util.List, Object) used to retrieve the range of vbits defined and used by the statement.

Determine the variables defined and used by the instruction. This method is an extended version of getDefUse(List, List, Object).@return

Retrieve the optional stack-pointer delta indicator. The SP delta represents the native delta in bytes, relative to SP0 (stack pointer at the underlying native routine entry-point), before the closest matching native instruction is executed.

Determine if this IR is a conditional IEJump, i.e. getCondition() is not null.

Determine if this IR is a simple goto, that is, an unconditional IEJump, i.e. getCondition() is null.

Called once by the normalizer component in later stages. Implementations may perform IRE replacement, unlike updateTypes's.

Called once by the type setter component during the typing stage, before propagating all types to the IR elements. Implementations may perform IRE replacement, unlike updateTypes's.

Remove a native instruction address from the list of mappings.

Replace (deep) the variables that are defined by this statement.

Replace (deep) the variables that are defined by this statement.

Deep replace. Specialized version allows used-vars replacement only. The implementation is responsible for IRE duplication before statements, to ensure that the resulting statement or group of statement does not contain duplicate references to mutable objects.

Reset the current mapping for native instruction addresses for this statement.

Reset the current mapping for native instruction addresses for this statement.

Reset the current mapping and add a single native instruction address mapping to this IR statement. Watch out! A statement should at least have one associated native address.

Reset the current mapping and add a collection of native instructions addresses mapping to this IR statement. Watch out! A statement should at least have one associated native address.

Set an optional stack-pointer delta indicator. The SP delta represents the native delta in bytes, relative to SP0 (stack pointer at the underlying native routine entry-point), before the closest matching native instruction is executed.

Depth-first search, pre-order visit of this statement. The node being visited may be replaced, but the client code is responsible for EVisitResults#setReplacedNode(IEGeneric) notifying the visitor.

Pre-order visits offer more options than post order visits: the visitor may decide to skip children; to skip the destination of assignments. However, replacement of nodes requires additional code to register the new node. Conversely, post-order visits do not offer any specific option, but provide the simplest way to replace nodes.

Depth-first search, pre-order visit of this statement. The node being visited may be replaced, but the client code is responsible for EVisitResults#setReplacedNode(IEGeneric) notifying the visitor.

Pre-order visits offer more options than post order visits: the visitor may decide to skip children; to skip the destination of assignments. However, replacement of nodes requires additional code to register the new node. Conversely, post-order visits do not offer any specific option, but provide the simplest way to replace nodes.

Depth-first search, post-order visit of this statement. The node being visited may be replaced without notifying the visitor.

Pre-order visits offer more options than post order visits: the visitor may decide to skip children; to skip the destination of assignments. However, replacement of nodes requires additional code to register the new node. Conversely, post-order visits do not offer any specific option, but provide the simplest way to replace nodes.

Retrieve an indication regarding whether this statement writes to memory.