We can step into false-positive memory leak if we reassign global variables
which assume memory allocations, for example std::string. Our unit tests has
embedded memory leak detector which gets inited/destroyed somewhere in the
middle of the test run. Hence allocations/deallocations done before/after its
active livetime will be transparent for it.
This particular case reassigned std::string global variable to the same value.
Apperantly my version of libstdc++ (the one on CentOS 7) did not recognize
that input/output string size is actually the same.
Signed-off-by: Dmitry Rogozhkin <dmitry.v.rogozhkin@intel.com>
https://github.com/intel/compute-runtime/pull/144
Change-Id: Iaab42588f59691d3085a4f8879d902076dcee0fb
Move code related to batch buffer submission from flush to dedicated function
Add parameter to pass aub file name from AubCenter to AubManager
Change-Id: I20abb3c8bd92114b3bc9caa2a6291dc1bbddad2a
- pass hwInfo and localMemoryEnabled to AubCenter ctor
- initialize AubCenter in Platform:intialize() when Device is
created - only when CSR is not CsrHw
- move aub_center files to runtime/aub directory
Change-Id: Iceb4bf1cb2bb55b42d438502cca667a449f11411
