This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tree-optimization/63446] dangling reference results in confusing diagnostic from -Wuninitialized


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

--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Manuel LÃpez-IbÃÃez from comment #6)
> What about [...]

That's roughly what I describe in comment #2, amended by comment #3.

> It could be a matter of following the chain of VUSE->VDEF,
> which I think we already do for Wuninitialized.

IIRC we don't, and the file contains a comment saying that it would be
expensive. Actually, properly limiting the maximal depth of the walk (as is
done in several other passes) would make it cheap enough and we should probably
do it.

Note that if make_foo was static or inline, it wouldn't exist anymore in the
uninit pass.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]