On 26-10-24 13:36, Daniel Feenberg wrote:
This is very disappointing. Such moves may be frequent in other
languages, but I don't see it happening to much in my Fortran 95 code. I
suppose if subroutine arguments are copy-in/copy-out, that would be a
source of spurious messages, as could
On Fri, 25 Oct 2024, Paul Floyd via Valgrind-users wrote:
On 24-10-24 14:33, Daniel Feenberg via Valgrind-users wrote:
...
origins" would do that. Is there an option or other way to ask Valgrind to
be a little stricter, and flag the use of an unidentified variable in an
assignment, n
On 10/24/24, Daniel Feenberg via Valgrind-users wrote:
Is there an option or other way to ask
Valgrind to be a little stricter, and flag the use of an unidentified
variable in an assignment, not just in a condition?
No. You (and many other new users) have stumbled onto *the* colossal
deficie
On 24-10-24 14:33, Daniel Feenberg via Valgrind-users wrote:
I am a bit inexperienced with Valgrind which reports an uninitialized
variable in my 34,000 line program. But the message comes from a branch
deep in libgfortran. After some experimentation, I created the following
example program
I am a bit inexperienced with Valgrind which reports an uninitialized
variable in my 34,000 line program. But the message comes from a branch
deep in libgfortran. After some experimentation, I created the following
example program which demonstrates my difficulty:
cat -n test.for
1
