From b75b7d0999a8e7dc94f5b6d521058f7aac822cce Mon Sep 17 00:00:00 2001
From: Philip Rebohle <philip.rebohle@tu-dortmund.de>
Date: Mon, 27 Aug 2018 14:50:47 +0200
Subject: [PATCH] [dxvk] Simplify discardBuffer access flags

Specifying both read and write access is unnecessary, as the dirty
check will always return true for writes when it would also return
true for reads.
---
 src/dxvk/dxvk_context.cpp | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/src/dxvk/dxvk_context.cpp b/src/dxvk/dxvk_context.cpp
index c6bdbc60..84dfb1b6 100644
--- a/src/dxvk/dxvk_context.cpp
+++ b/src/dxvk/dxvk_context.cpp
@@ -876,11 +876,7 @@ namespace dxvk {
   
   void DxvkContext::discardBuffer(
     const Rc<DxvkBuffer>&       buffer) {
-    DxvkAccessFlags accessFlags(
-      DxvkAccess::Read,
-      DxvkAccess::Write);
-    
-    if (m_barriers.isBufferDirty(buffer->slice(), accessFlags))
+    if (m_barriers.isBufferDirty(buffer->slice(), DxvkAccess::Write))
       this->invalidateBuffer(buffer, buffer->allocPhysicalSlice());
   }