https://bugs.kde.org/show_bug.cgi?id=413251
--- Comment #6 from Carl Ponder ---
I wouldn't have a clue how.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=413251
Carl Ponder changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|NOT A BUG
https://bugs.kde.org/show_bug.cgi?id=413251
Carl Ponder changed:
What|Removed |Added
Resolution|--- |NOT A BUG
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=413251
Carl Ponder changed:
What|Removed |Added
CC||cpon...@nvidia.com
--- Comment #1 from Carl
https://bugs.kde.org/show_bug.cgi?id=413251
Bug ID: 413251
Summary: Compilation error using GCC 7.4.0 & OpenMPI 4.0.2
Product: valgrind
Version: 3.15 SVN
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #24 from Carl Ponder <cpon...@nvidia.com> ---
I can upload an executable, or I can give you the source-code for the test and
instructions on how to build and run it.
You'd still need to have the PGI runtime installed. I can help y
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #22 from Carl Ponder <cpon...@nvidia.com> ---
I know they're not zeroing out the space.
As far as trying to intercept the subroutine-call, I've worked a little on this
level
coregrind/m_syswrap
but these only intercept system
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #18 from Carl Ponder <cpon...@nvidia.com> ---
PGI confirms that this call to "__builtin_aa" is what's bumping the stack
pointer. It's a subroutine inside the PGI runtime.
Does valgrind have a way for us to intercept this
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #17 from Carl Ponder <cpon...@nvidia.com> ---
I uploaded the two assembly-files. From the "sdiff", I think this is where the
allocations vary:
-Mnostack_arrays
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #16 from Carl Ponder <cpon...@nvidia.com> ---
Created attachment 102409
--> https://bugs.kde.org/attachment.cgi?id=102409=edit
Assembly generated with stack arrays, where valgrind doesn't work
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #15 from Carl Ponder <cpon...@nvidia.com> ---
Created attachment 102408
--> https://bugs.kde.org/attachment.cgi?id=102408=edit
Assembly generated without stack-arrays, where valgrind works
--
You are receiving this mail bec
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #13 from Carl Ponder <cpon...@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 rec
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #11 from Carl Ponder <cpon...@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
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #10 from Carl Ponder <cpon...@nvidia.com> ---
Stopping at line 70 puts it right after the array-allocation but before the
array-writes are happening:
62 implicit none
63 integer, intent(in) :: N
64 integer ( ki
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #8 from Carl Ponder <cpon...@nvidia.com> ---
If I *don't* compile with the -Mstack_arrays, I get this at line 77 instead:
(gdb) print x
$1 = (0, 1, 2, 3, 4, 0, 0, 0, 0, 0)
(gdb) print
$2 = (PTR TO -> ( integer (10))) 0x7088
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #7 from Carl Ponder <cpon...@nvidia.com> ---
Ok here's better -- I can see the data if I compile using "-O0 -g" rather than
"-O0 -gopt", which I'd assumed would be the same thing.
Here's what I'm seeing in th
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #4 from Carl Ponder <cpon...@nvidia.com> ---
Can you please list out the commands more precisely?
I ran these commands in one window:
module purge
module load pgi/16.9
module load gcc/4.8.5
module load va
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #3 from Carl Ponder <cpon...@nvidia.com> ---
This "pgfortran" is the PGI Fortran compiler.
What I'm puzzled about is why valgrind is finding more uninitialized
array-elements when I compiled with gfortran than with pgfortr
https://bugs.kde.org/show_bug.cgi?id=371966
--- Comment #1 from Carl Ponder <cpon...@nvidia.com> ---
I attached the test-case here. You can reproduce the issue as follows:
pgfortran -o test03.pgi test03.f90 -O0 -gopt
valgrind test03.pgi # 12 errors.
pgfortran -o test
https://bugs.kde.org/show_bug.cgi?id=371966
Bug ID: 371966
Summary: No uninitialised values reported with PGI
-Mstack_arrays
Product: valgrind
Version: 3.11.0
Platform: unspecified
OS: Linux
20 matches
Mail list logo
