4 Commits

Author	SHA1	Message	Date
Miklos Vajna	bf0d49c437	clang-rename: let -force handle multiple renames ... Summary: The use case is that renaming multiple symbols in a large enough codebase is much faster if all of these can be done with a single invocation, but there will be multiple translation units where one or more symbols are not found. Old behavior was to exit with an error (default) or exit without reporting an error (-force). New behavior is that -force results in a best-effort rename: rename symbols which are found and just ignore the rest. The existing help for -force sort of already implies this behavior. Reviewers: cfe-commits, klimek, arphaman Reviewed By: klimek Differential Revision: https://reviews.llvm.org/D37634 llvm-svn: 312942	2017-09-11 20:18:38 +00:00
Benjamin Kramer	1fec6cbeba	[clang-rename] Just return instead of calling exit(3) from main. ... llvm-svn: 306873	2017-06-30 20:24:32 +00:00
Alex Lorenz	f0d6169edd	Attempt to fix the linkage error caused by r306840 on the mingw-RA-on-linux bot ... llvm-svn: 306844	2017-06-30 17:15:48 +00:00
Alex Lorenz	4abbd92bf4	[refactor] Move clang-rename into the clang repository ... The core engine of clang-rename will be used for local and global renames in the new refactoring engine, as mentioned in http://lists.llvm.org/pipermail/cfe-dev/2017-June/054286.html. The clang-rename tool is still supported but might get deprecated in the future. Differential Revision: https://reviews.llvm.org/D34696 llvm-svn: 306840	2017-06-30 16:36:09 +00:00