diff options
| author | Alexandre Ganea <alexandre.ganea@ubisoft.com> | 2018-11-05 19:14:10 +0000 |
|---|---|---|
| committer | Alexandre Ganea <alexandre.ganea@ubisoft.com> | 2018-11-05 19:14:10 +0000 |
| commit | 3b9b4d2156673edda50584086fbfb0d66460b4d2 (patch) | |
| tree | 0a1ce1d7439b1d892da989391f83a9c637fd0bce /lldb/packages/Python/lldbsuite/test/lldbtest.py | |
| parent | 2b7ae47ccb5039a3716e637a91f4f65833decbc4 (diff) | |
| download | bcm5719-llvm-3b9b4d2156673edda50584086fbfb0d66460b4d2.tar.gz bcm5719-llvm-3b9b4d2156673edda50584086fbfb0d66460b4d2.zip | |
Only call FlushFileBuffers() when writing executables on Windows
This is a follow-up for "r325274: Call FlushFileBuffers on output files."
Previously, FlushFileBuffers() was called in all cases when writing a file. The objective was to go around a bug in the Windows kernel (as described here: https://randomascii.wordpress.com/2018/02/25/compiler-bug-linker-bug-windows-kernel-bug/). However that is required only when writing EXEs, any other file type doesn't need flushing.
This patch calls FlushFileBuffers() only for EXEs. In addition, we completly disable FlushFileBuffers() for known Windows 10 versions that do not exhibit the original kernel bug.
Differential Revision: https://reviews.llvm.org/D53727
llvm-svn: 346152
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbtest.py')
0 files changed, 0 insertions, 0 deletions
