[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 19:33:58
Message-ID: bug-371966-17878-Tu7aTHeq7E () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #13 from Carl Ponder <CPonder@nVidia.Com> ---
Given that there's junk in the array, I know that the contents aren't being
zero'd out, and the PGI people confirm that -Mstack_arrays are not initialized.
How does valgrind recognize that an array is being initialized under the
circumstances? Is it following the control-flow instruction-by-instruction?

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