This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/47444] False warning: array subscript is above array bounds
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 24 Jan 2011 22:21:29 +0000
- Subject: [Bug c++/47444] False warning: array subscript is above array bounds
- Auto-submitted: auto-generated
- References: <bug-47444-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47444
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
--- Comment #3 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2011-01-24 22:21:26 UTC ---
(In reply to comment #2)
> I didn't really follow in detail what we have been doing about these warnings,
> but submitter may have a point that the warning should not say "is above", and
> instead say something like "may be above". Manuel what do you think?
I think these warnings are exactly like uninitialized warnings. GCC can
sometimes prove that it happens but most of the time it can only be proved that
it "may" happen. Contrary to Wuninitialized, I am not sure that GCC analysis in
this warning is powerful enough to try to detect this difference, so I would
say, yes, using "may be" should be more appropriate.
But I think you better ask the corresponding maintainers, they are the ones
that will decide.