http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #6 from Steve Kargl ---
On Wed, Jan 01, 2014 at 05:02:53AM +, Thomas.L.Clune at nasa dot gov wrote:
>
> Ignore that output from Valgind. I was logged out between building and
> running, and failed to reload the appropriate enviro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #5 from tlcclt ---
Ignore that output from Valgind. I was logged out between building and
running, and failed to reload the appropriate environment. With the correct
environment, I get a clean run from valgrind:
valgrind ./a.out
==
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #4 from tlcclt ---
OK - had a bit of time waiting for the New Year countdown … so read up a bit
on valgrind.
A vanilla run under Linux with 4.9.0 gave the following, which seems
encouraging, albeit cryptic:
% gfortran -O0 -g allino
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
--- Comment #3 from tlcclt ---
I have testend under OS X (10.8.5) with gfortran 4.8.1 and 4.8.2. I've also
tested under Linux (not sure which flavor) with 4.9.0.
Command line is:
% gfortran allinone.F90
% ./a.out
Error - incorrect number of t
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
kargl at gcc dot gnu.org changed:
What|Removed |Added
CC||kargl at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59654
tlcclt changed:
What|Removed |Added
CC||Thomas.L.Clune at nasa dot gov
--- Comment #1 fr
