with intel inspector I noticed that a very small code like this
void test(int l)
char * s = new char[l];
int main(int argc, char *argv)
triggers a mismatched allocation/deallocation for the variable s;
This only occurs after stl headers are included (like the iostream here in this example)
Is it a bug of intel inspector ?
For background information, I'm using Visual Studio 2015, intel compiler 16 update 3, and Inspector XE 2016 Update 3 (in Parallel Studio).
Thanks for your feedbacks.
For more complete information about compiler optimizations, see our Optimization Notice.