[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays
From:       Carl Ponder <bugzilla_noreply () kde ! org>
Date:       2016-11-22 17:36:25
Message-ID: bug-371966-17878-yTf72l6fat () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=371966

--- Comment #11 from Carl Ponder <CPonder@nVidia.Com> ---
Back to comment #9, there *is* no instruction initializing the array, which is
why it has some junk entries, regardless of valgirind's lack of mention.

Talking to the PGI people, the -Mxtack_arrays flag causes the local arrays to
be allocated on the stack, so the allocation is just a matter of adjusting the
stack-pointer, rather than invoking "malloc" or equivalent.

Does valgrind work by intercepting the malloc calls and then tabulating the
uninitialized memory-cells? And if the arrays are allocated off of the stack in
gfortran or gcc, how would valgrind keep track of this?

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]