Duncan P. N. Exon Smith 1526278443 UseListOrder: Fix blockaddress use-list order ... `parseBitcodeFile()` uses the generic `getLazyBitcodeFile()` function as a helper. Since `parseBitcodeFile()` isn't actually lazy -- it calls `MaterializeAllPermanently()` -- bypass the unnecessary call to `materializeForwardReferencedFunctions()` by extracting out a common helper function. This removes the last of the use-list churn caused by blockaddresses. This highlights that we can't reproduce use-list order of globals and constants when parsing lazily -- but that's necessarily out of scope. When we're parsing lazily, we never have all the functions in memory, so the use-lists of globals (and constants that reference globals) are always incomplete. This is part of PR5680. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@214581 91177308-0d34-0410-b5e6-96231b3b80d8		2014-08-01 22:27:19 +00:00
..
Reader	UseListOrder: Fix blockaddress use-list order	2014-08-01 22:27:19 +00:00
Writer	UseListOrder: Handle self-users	2014-07-31 18:33:12 +00:00
CMakeLists.txt
LLVMBuild.txt
Makefile
module.modulemap	[modules] Add module maps for LLVM. These are not quite ready for prime-time	2014-05-21 02:46:14 +00:00