Dan Gohman 5c70fadc17 It's not possible to insert code immediately after an invoke in the ... same basic block, and it's not safe to insert code in the successor blocks if the edges are critical edges. Splitting those edges is possible, but undesirable, especially on the unwind side. Instead, make the bottom-up code motion to consider invokes to be part of their successor blocks, rather than part of their parent blocks, so that it doesn't push code past them and onto the edges. This fixes PR12307. llvm-svn: 153343		2012-03-23 17:47:54 +00:00
clang	Update checker build.	2012-03-23 07:06:16 +00:00
compiler-rt	[ASan/tests] Make 'noinline' and a bunch of other stuff portable	2012-03-23 13:10:59 +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	It appears that the standard accidentally removed the default constructor for error_category. I'm putting it back in. This fixes http://llvm.org/bugs/show_bug.cgi?id=12321.	2012-03-21 16:18:57 +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	Test website auto-update.	2012-03-20 18:22:49 +00:00
lldb	Fix a typo.	2012-03-23 01:28:19 +00:00
llvm	It's not possible to insert code immediately after an invoke in the	2012-03-23 17:47:54 +00:00
polly	CodeGen: Remove the need for setIVS	2012-03-23 12:20:36 +00:00