[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:       Philippe Waroquiers <bugzilla_noreply () kde ! org>
Date:       2016-11-22 20:02:36
Message-ID: bug-371966-17878-YZVQEtuFTG () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #14 from Philippe Waroquiers <philippe.waroquiers@skynet.be> ---
(In reply to Carl Ponder from comment #13)
> 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?

For Arrays allocated on the heap, the memory is marked uninitialised
when allocated.

For Arrays on the stack (more generally for all stacks variables),
the vars are marked as uninitialised when the stack pointer is decreased
to create the frame.

So, what might happen maybe with the fortran coompiler is that
they do not decrease/increase the SP for each function call
and/or for each scope 
or whatever.

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