clobbered warning

[Tim Bedding <tim at polyhedra dot com>]

> > Either the documentation or the implementation is incorrect.
> > I suggest the latter.

> Yes, this looks like a bug.

Thanks for the reply, Martin. Do you agree with me that
the implementation is incorrect? Or is it the documentation?

Either way, should I be looking at providing a patch
for this part?


> This warning is part of the -Wuninitialized warnings. As documented,
> the warnings are not produced if not optimizing. This is not an
> arbitrary choice; the information to produce the warning is just not
> computed when not optimizing.

I understand. I personally find it a little inconsistent to warn in one case and not
another. I guess the documentation could be made to explicitly state that the warning
is not produced simply because the information is not to hand.


> I don't know whether this is possible. If you find a way, please
> submit the corresponding patch to gcc-patches@gcc.gnu.org.

I am pretty sure that it is possible. Would gcc-patches be the appropriate
place to post my thoughts on how it could be implemented?
Or do they only want actual code implementations?

Is there any way to know whether I would be duplicating effort if I were to have
a go at this?

Cordially
Tim