[Bug fortran/30438] Set but never used variable should raise warning

[juergen.reuter at desy dot de]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

Jürgen Reuter  changed:

   What|Removed |Added

 CC||juergen.reuter at desy dot de

--- Comment #10 from Jürgen Reuter  ---
nagfor does this warning, ifort and PGI fortran doesn't.

[Bug fortran/30438] Set but never used variable should raise warning

[dominiq at lps dot ens.fr]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

--- Comment #9 from Dominique d'Humieres  ---
*** Bug 33884 has been marked as a duplicate of this bug. ***

[Bug fortran/30438] Set but never used variable should raise warning

[janus at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

janus at gcc dot gnu.org changed:

   What|Removed |Added

   See Also||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=61181
 CC||Joost.VandeVondele at mat dot 
ethz
   ||.ch

--- Comment #8 from janus at gcc dot gnu.org ---
*** Bug 61181 has been marked as a duplicate of this bug. ***

[Bug fortran/30438] Set but never used variable should raise warning

[dfranke at gcc dot gnu dot org]

--- Comment #5 from dfranke at gcc dot gnu dot org  2010-05-01 12:39 ---
With gcc version 4.6.0 20100501 (experimental) (GCC)

$ cat unused.c
int main() {
  int i;
  i = 42;
  return 0;
}

$ gcc-svn -Wall unused.c
unused.c: In function 'main':
unused.c:2:7: warning: variable 'i' set but not used
[-Wunused-but-set-variable]

Gfortran does not issue any warning with a similar fortran testcase.


Strangely, grepping the sources for use of the flag
'warn_unused_but_set_variable', I only find:

$ grep -r warn_unused_but_set_variable *
ChangeLog:  * toplev.c (warn_unused_but_set_variable): Default to
warn_unused.
common.opt:Common Var(warn_unused_but_set_variable) Init(-1) Warning
toplev.c:  if (warn_unused_but_set_variable == -1)
toplev.c:warn_unused_but_set_variable = warn_unused;

which is slightly less than expected - where/how is this flag used?!


-- 

dfranke at gcc dot gnu dot org changed:

   What|Removed |Added

 CC||dfranke at gcc dot gnu dot
   ||org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

[Bug fortran/30438] Set but never used variable should raise warning

[dfranke at gcc dot gnu dot org]

--- Comment #6 from dfranke at gcc dot gnu dot org  2010-05-01 14:25 ---
See also PR33884.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

[Bug fortran/30438] Set but never used variable should raise warning

[jakub at gcc dot gnu dot org]

--- Comment #7 from jakub at gcc dot gnu dot org  2010-05-01 18:28 ---
You should grep for unused_but_set_, then you'll see also:
c-decl.c:OPT_Wunused_but_set_variable,
c-decl.c:  if (warn_unused_but_set_parameter)
c-decl.c:  OPT_Wunused_but_set_parameter,

See http://gcc.gnu.org/viewcvs?root=gccview=revrev=158086


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

[Bug fortran/30438] Set but never used variable should raise warning

[aldot at gcc dot gnu dot org]

--- Comment #4 from aldot at gcc dot gnu dot org  2007-12-14 09:11 ---
Abovementioned C PR is PR18624 .


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438

[Bug fortran/30438] Set but never used variable should raise warning

[fxcoudert at gcc dot gnu dot org]

-- 

fxcoudert at gcc dot gnu dot org changed:

   What|Removed |Added

   Severity|normal  |enhancement
 Status|UNCONFIRMED |NEW
 Ever Confirmed|0   |1
   Last reconfirmed|-00-00 00:00:00 |2007-02-01 12:26:47
   date||
Summary|Unused variable should raise|Set but never used variable
   |warning with -Wunused   |should raise warning


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30438