FlowInformation

Empty flow information: the instruction modifies the flow of execution, but no target is explicitly specified.

Empty flow information, and implicit fall-through is disabled: the instruction modifies the flow of execution, but no target is explicitly specified. This constant is suitable for bad or tentative call-to-subs for which the return-to-caller is uncertain.

No flow information: the instruction does not modify the flow of execution.

Create an object with an empty target list, no post-compute fall-through, and no delay-slot (default). Note: this object indicates that the flow is changing, regardless of whether of not the target list will be populated. To indicate no-change in flow, a user should use NONE.

Create an object with an empty target list. Note: this object indicates that the flow is changing, regardless of whether of not the target list will be populated. To indicate no-change in flow, a user should use NONE.

Add a target to the list of possible targets.

Add a collection of targets to the list of possible targets.

Get the number of instructions in the delay slot.

Get the a list of targets. Be careful, this list does not include the fall-through target if it is implied (eg, when flow-info is returned by getRoutineCall(long)) or when its calculation was requested dynamically (via mustComputeFallThrough()).

Determine if this object does contain flow information.

Determine if this object does contain flow information and all targets are known.

Determine if this object does contain flow information but has no known targets.

IMPORTANT: if this flow info object is mixed (it specifies having unknown target(s), and also bears known targets), this method returns false.

Indicate if the flow information includes a fall-through address (relative to the current instruction) that is not present in the FlowInfo object itself. If this method returns true, the caller must dynamically calculate the fall-through address itself.

Note that the creator of a flowinfo object may decide to add the fall-through (if any) in the flowinfo object target list. However, in some cases, such as branching instructions with delay slot(s), it is simpler to indicate that the branching instruction allows a fall-through flow, but that it should be computed by the client/user, instead of stored or computed by the flowinfo object.

Indicate whether this flow information forbids the implicit calculation of a fall-through edge. (A fall-through may be explicitly specified as a target, regardless.)