2020
DOI: 10.1631/fitee.1900213
|View full text |Cite
|
Sign up to set email alerts
|

Modified condition/decision coverage (MC/DC) oriented compiler optimization for symbolic execution

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2021
2021
2024
2024

Publication Types

Select...
3

Relationship

0
3

Authors

Journals

citations
Cited by 3 publications
(1 citation statement)
references
References 48 publications
0
1
0
Order By: Relevance
“…This means that, at the current program point, the execution flow is more likely to execute reaching the goal point if the critical constraints are satisfied. Critical constraint only depends on a condition instead of a decision [15]. To identify the critical constraint, the first thing we need to do is converting a decision into one or more condition guards, for example, as shown in Figure 1, sum== 0 && m==100 is a decision while sum==0 and m==100 are condition guards respectively.…”
Section: Critical Constraint Recognitionmentioning
confidence: 99%
“…This means that, at the current program point, the execution flow is more likely to execute reaching the goal point if the critical constraints are satisfied. Critical constraint only depends on a condition instead of a decision [15]. To identify the critical constraint, the first thing we need to do is converting a decision into one or more condition guards, for example, as shown in Figure 1, sum== 0 && m==100 is a decision while sum==0 and m==100 are condition guards respectively.…”
Section: Critical Constraint Recognitionmentioning
confidence: 99%