Flawfinder version 2.0.10, (C) 2001-2019 David A. Wheeler.
Number of rules (primarily dangerous function names) in C/C++ ruleset: 223
Examining data/readerwriterqueue-1.0.3/atomicops.h
Examining data/readerwriterqueue-1.0.3/benchmarks/bench.cpp
Examining data/readerwriterqueue-1.0.3/benchmarks/ext/1024cores/spscqueue.h
Examining data/readerwriterqueue-1.0.3/benchmarks/ext/folly/ProducerConsumerQueue.h
Examining data/readerwriterqueue-1.0.3/benchmarks/systemtime.cpp
Examining data/readerwriterqueue-1.0.3/benchmarks/systemtime.h
Examining data/readerwriterqueue-1.0.3/readerwriterqueue.h
Examining data/readerwriterqueue-1.0.3/tests/common/simplethread.cpp
Examining data/readerwriterqueue-1.0.3/tests/common/simplethread.h
Examining data/readerwriterqueue-1.0.3/tests/stabtest/stabtest.cpp
Examining data/readerwriterqueue-1.0.3/tests/unittests/minitest.h
Examining data/readerwriterqueue-1.0.3/tests/unittests/unittests.cpp

FINAL RESULTS:

data/readerwriterqueue-1.0.3/benchmarks/ext/1024cores/spscqueue.h:106:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
  char cache_line_pad_ [cache_line_size]; 
data/readerwriterqueue-1.0.3/readerwriterqueue.h:687:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char cachelineFiller0[MOODYCAMEL_CACHE_LINE_SIZE - sizeof(weak_atomic<size_t>) - sizeof(size_t)];
data/readerwriterqueue-1.0.3/readerwriterqueue.h:691:3:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
		char cachelineFiller1[MOODYCAMEL_CACHE_LINE_SIZE - sizeof(weak_atomic<size_t>) - sizeof(size_t)];	// next isn't very contended, but we don't want it on the same cache line as tail (which is)
data/readerwriterqueue-1.0.3/readerwriterqueue.h:732:2:  [2] (buffer) char:
  Statically-sized arrays can be improperly restricted, leading to potential
  overflows or other issues (CWE-119!/CWE-120). Perform bounds checking, use
  functions that limit length, or ensure that the size is larger than the
  maximum possible length.
	char cachelineFiller[MOODYCAMEL_CACHE_LINE_SIZE - sizeof(weak_atomic<Block*>)];
data/readerwriterqueue-1.0.3/benchmarks/ext/folly/ProducerConsumerQueue.h:63:14:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
      while (read != end) {
data/readerwriterqueue-1.0.3/benchmarks/ext/folly/ProducerConsumerQueue.h:64:18:  [1] (buffer) read:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
        records_[read].~T();
data/readerwriterqueue-1.0.3/benchmarks/systemtime.cpp:71:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	::usleep(milliseconds * 1000);
data/readerwriterqueue-1.0.3/benchmarks/systemtime.cpp:107:4:  [1] (obsolete) usleep:
  This C routine is considered obsolete (as opposed to the shell command by
  the same name). The interaction of this function with SIGALRM and other
  timer functions such as sleep(), alarm(), setitimer(), and nanosleep() is
  unspecified (CWE-676). Use nanosleep(2) or setitimer(2) instead.
	::usleep(milliseconds * 1000);
data/readerwriterqueue-1.0.3/tests/unittests/unittests.cpp:789:3:  [1] (buffer) getchar:
  Check buffer boundaries if used in a loop including recursive loops
  (CWE-120, CWE-20).
		getchar();

ANALYSIS SUMMARY:

Hits = 9
Lines analyzed = 3795 in approximately 0.09 seconds (40891 lines/second)
Physical Source Lines of Code (SLOC) = 2876
Hits@level = [0]  25 [1]   5 [2]   4 [3]   0 [4]   0 [5]   0
Hits@level+ = [0+]  34 [1+]   9 [2+]   4 [3+]   0 [4+]   0 [5+]   0
Hits/KSLOC@level+ = [0+] 11.822 [1+] 3.12935 [2+] 1.39082 [3+]   0 [4+]   0 [5+]   0
Dot directories skipped = 1 (--followdotdir overrides)
Minimum risk level = 1
Not every hit is necessarily a security vulnerability.
There may be other security vulnerabilities; review your code!
See 'Secure Programming HOWTO'
(https://dwheeler.com/secure-programs) for more information.