Community
cancel
Showing results for 
Search instead for 
Did you mean: 
82 Views

Leak memory with -parallel option

Hi all,

compiling the following code with icc -parallel resulys in memory leak (valgrind sense):
icc -parallel test.c && ./a.out

test.c

valgrind --leak-check=full --show-reachable=yes ./a.out

test.out.icc

Compiling the same code with gcc (gcc (Debian 4.3.2-1.1) 4.3.2) doesn't result in a memory leak.

test.out.gcc

My platform is 2.6.29-bpo.2-686 #1 SMP Mon May 18 16:08:51 UTC 2009 i686 GNU/Linux,
by similar results occurs on 2.6.18-5-amd64 #1 SMP Sat Dec 22 20:43:59 UTC 2007 x86_64 GNU/Linux,
2.6.18-6-amd64 #1 SMP Sat Feb 20 23:34:55 UTC 2010 x86_64 GNU/Linux

I use icc (ICC) 11.1 20090511, but same results occurs with icc (ICC) 11.1 20100806 .
valgrind version is valgrind-3.6.0.SVN

Any suggestion is welcome.

F.T.

0 Kudos
1 Reply
82 Views

Ops,
I'm confused.

I just found on valgrind's website

http://valgrind.org/docs/manual/dist.news.html

* KNOWN LIMITATIONS:

- Memcheck is unusable with the Intel compiler suite version 11.1,
when it generates code for SSE2-and-above capable targets. This
is because of icc's use of highly optimised inlined strlen
implementations. It causes Memcheck to report huge numbers of
false errors even in simple programs. Helgrind and DRD may also
have problems.

Versions 11.0 and earlier may be OK, but this has not been
properly tested.


that previous post was in fact a false positive valgrind's comlaint.

F.T.
Reply