Argyrios Kyrtzidis 9d7c0fef65 [code-complete] Introduce CodeCompletionTUInfo which will be used for caching ... code-completion related strings specific to a translation unit (ASTContext and related data) CodeCompletionAllocator does such limited caching, by caching the name assigned to a DeclContext*, but that is not the appropriate place since that object has a lifetime that can extend beyond that of an ASTContext. Introduce CodeCompletionTUInfo which will be always tied to a translation unit to do this kind of caching and move the caching of CodeCompletionAllocator into this object, and propagate it to all the places where it will be needed. The plan is to extend the caching where appropriate, using CodeCompletionTUInfo, to avoid re-calculating code-completion strings. Part of rdar://10796159. llvm-svn: 154408		2012-04-10 17:23:48 +00:00
clang	[code-complete] Introduce CodeCompletionTUInfo which will be used for caching	2012-04-10 17:23:48 +00:00
compiler-rt	Change the way ASan interacts with custom signal handlers.	2012-04-10 11:00:26 +00:00
debuginfo-tests	Revert previous patch as the corresponding clang patch was reverted.	2012-01-26 07:01:33 +00:00
libclc	Switch to BSD/MIT dual license.	2012-02-22 04:47:39 +00:00
libcxx	Fix the remaining atomic tests, all of which were wrong for the case where a	2012-04-05 13:48:16 +00:00
libcxxabi	I would really like to write the handlers in terms of C++11 atomics. This would give us the best performance, portablity, and safety tradeoff. Unfortunately I can not yet do that. So I've put the desired code in comments, and reverted the handler getters to the slower but safer legacy atomic intrinsics.	2012-03-19 16:56:51 +00:00
lld	[docs] Remove a dead link.	2012-04-10 16:18:16 +00:00
lldb	Added a new packet to our GDB remote protocol:	2012-04-10 03:22:03 +00:00
llvm	Remove unused variable.	2012-04-10 15:23:13 +00:00
polly	Fix typos.	2012-04-09 19:46:05 +00:00