From 8a13bfd207a64361130b25b32fbdf8115b324d25 Mon Sep 17 00:00:00 2001
From: Christopher Jones <cdj@fnal.gov>
Date: Fri, 27 Jun 2014 15:21:39 +0200
Subject: [PATCH] Marked debugging static as thread safe in
 KinematicConstrainedVertexupdatorT

A static instance of a class which only has a std::atomic member data was being
falsely accused of being thread unsafe by the static analyzer. Given the rare
case this represents, it was easier to just mark the static as thread safe using
our C++11 attribute.
---
 .../KinematicFit/interface/KinematicConstrainedVertexUpdatorT.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/RecoVertex/KinematicFit/interface/KinematicConstrainedVertexUpdatorT.h b/RecoVertex/KinematicFit/interface/KinematicConstrainedVertexUpdatorT.h
index ba23412d10e64..ac28f6d24bfb4 100644
--- a/RecoVertex/KinematicFit/interface/KinematicConstrainedVertexUpdatorT.h
+++ b/RecoVertex/KinematicFit/interface/KinematicConstrainedVertexUpdatorT.h
@@ -18,7 +18,7 @@ namespace KineDebug3 {
 
   };
   inline void count() {
-    static Count c;
+    [[cms::thread_safe]] static Count c;
     ++c.n;
   }