Duncan P. N. Exon Smith 789d5bf211 UseListOrder: Visit global values ... When predicting use-list order, we visit functions in reverse order followed by `GlobalValue`s and write out use-lists at the first opportunity. In the reader, this will translate to *after* the last use has been added. For this to work, we actually need to descend into `GlobalValue`s. Added a targeted test in `use-list-order.ll` and `RUN` lines to the newly passing tests in `test/Bitcode`. There are two remaining failures in `test/Bitcode`: - blockaddress.ll: I haven't thought through how to model the way block addresses change the order of use-lists (or how to work around it). - metadata-2.ll: There's an old-style `@llvm.used` global array here that I suspect the .ll parser isn't upgrading properly. When it round-trips through bitcode, the .bc reader *does* upgrade it, so the extra variable (`i8* null`) has an extra use, and the shuffle vector doesn't match. I think the fix is to upgrade old-style global arrays (or reject them?) in the .ll parser. This is part of PR5680. llvm-svn: 214321		2014-07-30 17:51:09 +00:00
..
Reader	Have a single enum for "not a bitcode" error.	2014-07-29 21:01:24 +00:00
Writer	UseListOrder: Visit global values	2014-07-30 17:51:09 +00:00
CMakeLists.txt
LLVMBuild.txt	LLVMBuild: Introduce a common section which currently has a list of the	2011-12-12 22:45:54 +00:00
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