[Bug middle-end/22197] invalid "is" used uninitialized, should be "may be"

2005-11-25 Thread gdr at gcc dot gnu dot org
--- Comment #4 from gdr at gcc dot gnu dot org 2005-11-26 07:44 --- (In reply to comment #2) > Hmm, sort of. The call of g(i) also warns with "is used", although I > think it might deserve only a "may be used". But anyway I think that > this nevertheless has different causes. It's n

[Bug middle-end/22197] invalid "is" used uninitialized, should be "may be"

2005-06-27 Thread schwab at suse dot de
--- Additional Comments From schwab at suse dot de 2005-06-27 13:57 --- In the case of g(i) you have an initialisation of the parameter variable which already constitutes a use of the value. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22197

[Bug middle-end/22197] invalid "is" used uninitialized, should be "may be"

2005-06-27 Thread matz at suse dot de
--- Additional Comments From matz at suse dot de 2005-06-27 13:50 --- Hmm, sort of. The call of g(i) also warns with "is used", although I think it might deserve only a "may be used". But anyway I think that this nevertheless has different causes. It's not the call creating the prob

[Bug middle-end/22197] invalid "is" used uninitialized, should be "may be"

2005-06-27 Thread pinskia at gcc dot gnu dot org
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-06-27 13:31 --- but isn't that the same as (except it is an aggregate in the case in comment #1): void g(int); void f(void) { int i; g(i); } because g might not look at the agrument value? -- What|Remo