Chris Lattner 106bba1e9b The new bytecode format supports emitting strings a special case. This is ... intended to save size (and does on small programs), but on big programs it actually increases the size of the program slightly. The deal is that many functions end up using the characters that the string contained, and the characters are no longer in the global constant table, so they have to be emitted in function specific constant pools. This pessimization will be fixed in subsequent patches. llvm-svn: 10864		2004-01-14 23:36:54 +00:00
..
Analysis	Remove use of ConstantHandling itf	2004-01-12 18:02:15 +00:00
AsmParser	Don't use ConstantExpr::getShift anymore	2004-01-12 19:08:43 +00:00
Bytecode	The new bytecode format supports emitting strings a special case. This is	2004-01-14 23:36:54 +00:00
CodeGen	Properly update #intervals statistic.	2004-01-14 10:44:29 +00:00
CWriter	Turn off "attribute weak" to pacify Mac OS X's system compiler, which prints a	2003-12-11 00:24:36 +00:00
Debugger	"fix" a nasty race condition	2004-01-14 21:18:03 +00:00
ExecutionEngine	Don't pass anything to the IntrinsicLowering class that is not_intrinsic,	2004-01-14 06:02:53 +00:00
Support	Remove use of ConstantHandling itf	2004-01-12 20:13:04 +00:00
Target	Eliminate the isStringCompatible function, using ConstantArray::isString.	2004-01-14 17:15:17 +00:00
Transforms	Fix InstCombine/2004-01-13-InstCombineInvokePHI.ll, which also fixes lots	2004-01-14 06:06:08 +00:00
VMCore	When emitting bytecode, handle strings specially. Do not add the characters	2004-01-14 23:34:39 +00:00
Makefile	Add new dir	2004-01-05 05:25:59 +00:00