egcs, possible c++/g++ bug, accessing uninitialized var + PATCH
Kaveh R. Ghazi
ghazi@caip.rutgers.edu
Mon Sep 28 11:29:00 GMT 1998
> From: "David S. Miller" <davem@dm.cobaltmicro.com>
>
> Date: Mon, 28 Sep 1998 09:44:10 -0400 (EDT)
> From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
>
> In tracking down one warning about an uninitialized
> variable, it appeared that this one clearly was getting accessed
> before being set.
>
> Please track these down for real.
Er, I thought that's exactly what I did.
> There are some apparent bugs in
> flow, Mark Mitchell has made note of these cases too, which cause
> these bogon warnings to be generated.
I'm not sure that's relevant here. I said in my report (see
above) that this wasn't a bogon warning. Visual inspection shows that
flow correctly flagged the spot. My hesitation was whether my patch was
right, not whether the warning was appropriate.
> I plan to look into this when time permits...
> Later,
> David S. Miller
Okay great. Fixing flow would be a big win.
--Kaveh
--
Kaveh R. Ghazi Engagement Manager / Project Services
ghazi@caip.rutgers.edu Icon CMT Corp.
More information about the Gcc-bugs
mailing list