Bob Haarman 50bb177930 LTO: don't fatal when value for cache key already exists ... Summary: LTO/Caching.cpp uses file rename to atomically set the value for a cache key. On Windows, this fails when the destination file already exists. Previously, LLVM would report_fatal_error in such cases. However, because the old and the new value for the cache key are supposed to be equivalent, it actually doesn't matter which one we keep. This change makes it so that failing the rename when an openable file with the desired name already exists causes us to report success instead of fataling. Reviewers: pcc, hans Subscribers: mehdi_amini, llvm-commits, hiraditya Differential Revision: https://reviews.llvm.org/D39874 llvm-svn: 317899		2017-11-10 17:08:21 +00:00
..
Caching.cpp	LTO: don't fatal when value for cache key already exists	2017-11-10 17:08:21 +00:00
CMakeLists.txt
LLVMBuild.txt
LTO.cpp	[LTO][ThinLTO] Use the linker resolutions to mark global values as dso_local.	2017-11-04 17:04:39 +00:00
LTOBackend.cpp	[Support] Rename tool_output_file to ToolOutputFile, NFC	2017-09-23 01:03:17 +00:00
LTOCodeGenerator.cpp	Add llvm::for_each as a range-based extensions to <algorithm> and make use of it in some cases where it is a more clear alternative to std::for_each.	2017-11-03 20:01:25 +00:00
LTOModule.cpp	LTOModule::isBitcodeFile() shouldn't assert when returning false.	2017-10-31 16:39:47 +00:00
ThinLTOCodeGenerator.cpp	Move the stripping of invalid debug info from the Verifier to AutoUpgrade.	2017-10-02 18:31:29 +00:00
UpdateCompilerUsed.cpp