llvm/llvm-project

[Attributor] Make use of analysis in the MustBeExecutedExplorer

Open

#175 opened on Mar 13, 2020

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C++ (10,782 forks)batch import
good first issuegsochelp wantedllvm::Attributor

Repository metrics

Stars
 (26,378 stars)
PR merge metrics
 (Avg merge 1d 2h) (1,000 merged PRs in 30d)

Description

Right now the MustBeExecutedContextExplorer Explorer is created without analysis, e.g., without a dominator tree. As a consequence it is not able to determine non-trivial control flow merge points which reduces the "must-be-executed-context" substantially.

The task is to provide the appropriate analysis getters to the Explorer during creation and update the tests accordingly. If tests for the new capabilities are missing, thus the affected tests do not show the expected effect, new tests need to be added.

Contributor guide

Research direction
Understand the MustBeExecutedContextExplorer class and identify which analysis getters (e.g., dominator tree) are needed. Then update the existing tests and add new ones to verify the improved behavior.
Tech stack
cpp
Domain
compilers
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
5
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50