Bill Wendling ac18929801 If there's more than one function operand to a call instruction, be conservative ... and don't assume that the call doesn't throw. It would be nice if there were a way to determine which is the callee and which is a parameter. In practice, the architecture we care about normally only have one operand for a call instruction (x86 and arm). git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@87023 91177308-0d34-0410-b5e6-96231b3b80d8		2009-11-12 20:51:53 +00:00
..
Analysis	"Attach debug info with llvm instructions" mode was enabled a month ago. Now make it permanent and remove old way of inserting intrinsics to encode debug info for line number and scopes.	2009-11-12 19:02:56 +00:00
Archive
AsmParser	Fix MSVC warning ( | with bool and unsigned int).	2009-11-07 23:51:55 +00:00
Bitcode
CodeGen	If there's more than one function operand to a call instruction, be conservative	2009-11-12 20:51:53 +00:00
CompilerDriver	Remove dead code.	2009-11-11 04:10:24 +00:00
ExecutionEngine	Use stubs when we have them, otherwise use code we already have,	2009-11-12 03:12:18 +00:00
Linker	Fix MemoryBuffer::getSTDIN to *not* return null if stdin is empty, this is a lame API.	2009-11-10 00:43:58 +00:00
MC
Support	Add compare_lower and equals_lower methods to StringRef. Switch all users of	2009-11-12 20:36:59 +00:00
System	Revert commit 81144, and add a comment. It caused bugpoint timeouts	2009-11-08 20:55:48 +00:00
Target	Add a bool flag to StackObjects telling whether they reference spill	2009-11-12 20:49:22 +00:00
Transforms	implement a nice little efficiency hack in the inliner. Since we're now	2009-11-12 07:56:08 +00:00
VMCore	Do not use StringRef in DebugInfo interface.	2009-11-12 00:50:58 +00:00
Makefile