Skip to content

Avoid adding auxiliary 'jimple' variables to the list of possible conflicts. #34

@barbosamaatheus

Description

@barbosamaatheus

Currently in the implementation of Overriding Assignment, when the 'jimple' creates additional auxiliary variables, these variables are added to the list of possible conflicts which generates a greater effort when it comes to flicting the real conflicts in this list and this consequently has an impact on performance . Avoiding adding these variables is a possible solution.

Example:

public class Sample{

    public void m() {
        int x = foo() + bar(); // LEFT    x = $stack2 + $stack3 // Jimple
        x = x + qux();         // RIGHT   x = x + $stack4 // Jimple
    }
    ...
}

In this example, $stack2, $stack3 and $stack4 are added to the list when, in fact, it was only necessary to add x

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions