pghs975uc
/
infer_clone
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9ad32bbbf0'
${ noResults }
infer_clone/infer/tests/codetoanalyze/cpp/frontend/namespace/namespace.dot

25 lines
716 B
Raw Normal View History Unescape

initial synchronization
10 years ago
digraph iCFG {
[clang frontend] Pre-process AST locations to make them explicit and easier to deal with. Don't dive into include files. Summary: @public The clang location information is described in an incremental way: each location information is a delta with respect to the previous one in the AST. This is based on a the visit of the AST nodes which corresponds to the order in which the lines are printed with the standard clang AST dump: clang -cc1 -ast-dump filename.c This diff adds a preprocessing phase to the front-end so that location information is composed during a visit, and explicit location information is used instead. In the case of include files, we report the last known location before including the file. The current file for a function is the file where it is defined. So if a function is entirely defined in a .h file, then the location information will consistently be about the .h file. If instead a function is defined in the source file being analyzed, and some AST nodes come from macro expansion, line information will refer to the original file. The front-end tests reveal that the location information was incorrect in a few dot files. Test Plan: arc unit, after having fixed the wrong location in the existing .dot files
10 years ago
6 [label="6: Return Stmt \n n$0=*&#GB$pi:double [line 25]\n *&return:double =(2 * n$0) [line 25]\n REMOVE_TEMPS(n$0); [line 25]\n APPLY_ABSTRACTION; [line 25]\n " shape="box"]
initial synchronization
10 years ago
6 -> 5 ;
5 [label="5: Exit value \n " color=yellow style=filled]
4 [label="4: Start value\nFormals: \nLocals: \n DECLARE_LOCALS(&return); [line 25]\n " color=yellow style=filled]
4 -> 6 ;
[clang frontend] Pre-process AST locations to make them explicit and easier to deal with. Don't dive into include files. Summary: @public The clang location information is described in an incremental way: each location information is a delta with respect to the previous one in the AST. This is based on a the visit of the AST nodes which corresponds to the order in which the lines are printed with the standard clang AST dump: clang -cc1 -ast-dump filename.c This diff adds a preprocessing phase to the front-end so that location information is composed during a visit, and explicit location information is used instead. In the case of include files, we report the last known location before including the file. The current file for a function is the file where it is defined. So if a function is entirely defined in a .h file, then the location information will consistently be about the .h file. If instead a function is defined in the source file being analyzed, and some AST nodes come from macro expansion, line information will refer to the original file. The front-end tests reveal that the location information was incorrect in a few dot files. Test Plan: arc unit, after having fixed the wrong location in the existing .dot files
10 years ago
3 [label="3: Return Stmt \n *&return:int =5 [line 12]\n APPLY_ABSTRACTION; [line 12]\n " shape="box"]
initial synchronization
10 years ago
3 -> 2 ;
2 [label="2: Exit value \n " color=yellow style=filled]
1 [label="1: Start value\nFormals: \nLocals: \n DECLARE_LOCALS(&return); [line 12]\n " color=yellow style=filled]
1 -> 3 ;
}