https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31447
Thomas Koenig changed:
What|Removed |Added
Last reconfirmed|2007-04-18 07:08:17 |2017-6-15
CC|
--- Comment #4 from jv244 at cam dot ac dot uk 2009-09-23 18:37 ---
(In reply to comment #3)
> a=RESHAPE((/(TRANSFER(uninitialized_a_type_dummy,uninitialized_a_type_dummy),i=1,SIZE(a))/),SHAPE(a))
the simpler:
a=RESHAPE((/(uninitialized_a_type_dummy,i=1,SIZE(a))/),SHAPE(a))
is of cour
--- Comment #3 from jv244 at cam dot ac dot uk 2009-09-19 11:37 ---
I've also run into this issue, it would be great if there would be a flag like
-finit-undefined-intentout (?), so that intent(out) variable would first be
undefined by the compiler (in a way that valgrind notices this wi
--- Comment #2 from burnus at gcc dot gnu dot org 2007-09-14 09:53 ---
Initializing INTENT(OUT) variables should not be the default with
-finit-local-zero; otherwise I'm in favour of this option.
See also PR 33430 for other omissions of the -finit-* patch (cf. PR 20441).
--
burnus a
--- Comment #1 from dfranke at gcc dot gnu dot org 2007-07-09 12:56 ---
Related: PR28004 - "Warn if intent(out) dummy variable is used before being
defined"
--
dfranke at gcc dot gnu dot org changed:
What|Removed |Added
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last recon
