Rafael Espindola d1beb07d39 Have a single way for creating unique value names. ... We had two code paths. One would create names like "foo.1" and the other names like "foo1". For globals it is important to use "foo.1" to help C++ name demangling. For locals there is no strong reason to go one way or the other so I kept the most common mangling (foo1). llvm-svn: 253804		2015-11-22 00:16:24 +00:00
..
basic.ll	Have a single way for creating unique value names.	2015-11-22 00:16:24 +00:00
call-in-loop.ll	[Statepoints] Support for "patchable" statepoints.	2015-05-12 23:52:24 +00:00
call_gc_result.ll	Have a single way for creating unique value names.	2015-11-22 00:16:24 +00:00
finite-loops.ll	[PowerPC] Add an MI SSA peephole pass.	2015-11-10 21:38:26 +00:00
invokes.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
memset.ll	Revert "Change memcpy/memset/memmove to have dest and source alignments."	2015-11-19 05:56:52 +00:00
patchable-statepoints.ll	[Statepoints] Let patchable statepoints have a symbolic call target.	2015-07-28 23:50:30 +00:00
split-backedge.ll	[Statepoints] Support for "patchable" statepoints.	2015-05-12 23:52:24 +00:00
statepoint-calling-conventions.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
statepoint-coreclr.ll	Add a GCStrategy for CoreCLR	2015-05-20 01:07:23 +00:00
statepoint-format.ll	Move the personality function from LandingPadInst to Function	2015-06-17 20:52:32 +00:00
statepoint-frameescape.ll	Rename llvm.frameescape and llvm.framerecover to localescape and localrecover	2015-07-07 22:25:32 +00:00