Rafael Espindola 9cb8841b77 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
..
2003-05-01-PHIProblem.ll
2003-08-23-EmptySwitch.ll
2004-03-13-SwitchIsDefaultCrash.ll
2014-06-10-SwitchContiguousOpt.ll	[opaque pointer type] Add textual IR support for explicit type parameter to load instruction	2015-02-27 21:17:42 +00:00
2014-06-11-SwitchDefaultUnreachableOpt.ll	[opaque pointer type] Add textual IR support for explicit type parameter to load instruction	2015-02-27 21:17:42 +00:00
2014-06-23-PHIlowering.ll
delete-default-block-crash.ll	[LowerSwitch] Fix a bug when LowerSwitch deletes the default block	2015-08-11 18:12:26 +00:00
feature.ll	Have a single way for creating unique value names.	2015-11-22 00:16:24 +00:00
fold-popular-case-to-unreachable-default.ll	LowerSwitch: replace unreachable default with popular case destination	2015-01-23 20:43:51 +00:00