8 Commits (7855d6ecfa5f6cd3c486be372277a0fb4afd6678)

Author	SHA1	Message	Date
Dulma Rodriguez	1e5b8aeee7	Adding builtin setters and using them by skip ... Summary: public This continues the work on adding builtins for getters and setters and removing the generated code from the frontend. This is extending it to setters and removing the preanalysis that is no longer needed. Reviewed By: akotulski Differential Revision: D2734499 fb-gh-sync-id: 7cf5749	9 years ago
Dulma Rodriguez	12d21c73dd	Adding builtins for getters and calling them by skip ... Summary: public We were generating getters and setters in the frontend, and then removing them if they were not needed in the preanalysis. This diff adds a builtin getter that gets called if we are going to skip the function. That means, if there was a getter written by the developers we still use that one rather than the builtin. Code for setter and cleanup of preanalysis will come in a next diff. Reviewed By: jvillard Differential Revision: D2702890 fb-gh-sync-id: d65f25e	9 years ago
Andrzej Kotulski	35bb8a9a26	Change order in which ids get generated for objcMessageExpr_trans ... Summary: public Make it uniform with other function call translations. This is just reordering, no functional change intended Reviewed By: dulmarod Differential Revision: D2696370 fb-gh-sync-id: 63656e3	9 years ago
Andrzej Kotulski	3f9a08f99c	Defer cfg node creation for returnStmt and init_expr_trans ... Summary: public Nodes in these functions can be created later (after translation of subexpressions is done). Change triggers many differences in .dot files, but they are all about different numbering of nodes. There is no functional change in this diff. Reviewed By: dulmarod Differential Revision: D2699703 fb-gh-sync-id: a7b8d2a	9 years ago
Dulma Rodriguez	d7655a087e	[clang] Adding getters and setters for all the methods	9 years ago
Cristiano Calcagno	3e199467f4	Complete copyright messages.	10 years ago
Cristiano Calcagno	10970c4f51	[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
Open Source Synchronization	b8982270f2	initial synchronization	10 years ago