Chandler Carruth 77b6e47f74 [PM] Improve the API and comments around the analysis manager proxies. ... These are really handles that ensure the analyses get cleared at appropriate places, and as such copying doesn't really make sense. Instead, they should look more like unique ownership objects. Make that the case. Relatedly, if you create a temporary of one and move out of it its destructor shouldn't actually clear anything. I don't think there is any code that can trigger this currently, but it seems like a more robust implementation. If folks want, I can add a unittest that forces this to be exercised, but that seems somewhat pointless -- whether a temporary is ever created in the innards of AnalysisManager is not really something we should be adding a reliance on, but I didn't want to leave a timebomb in the code here. If anyone has a cleaner way to represent this, I'm all ears, but I wanted to assure myself that this wasn't in fact responsible for another bug I'm chasing down (it wasn't) and figured I'd commit that. llvm-svn: 261594		2016-02-23 00:05:00 +00:00
..
llvm	[PM] Improve the API and comments around the analysis manager proxies.	2016-02-23 00:05:00 +00:00
llvm-c	Add support for invoke/landingpad/resume in C API test	2016-02-18 20:38:32 +00:00