https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
Martin Sebor changed:
What|Removed |Added
Keywords||diagnostic
Status|UNCONFIRMED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
Paolo Carlini changed:
What|Removed |Added
CC|gcc-bugs at gcc dot gnu.org |
--- Comment #7 from Paolo Carlini 2012-
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
--- Comment #6 from Paolo Carlini 2011-10-15
21:30:07 UTC ---
Should this be target or middle-end instead of c++? (I have no easy way to
check whether it's still an issue today)
--- Comment #5 from caolanm at redhat dot com 2009-10-31 17:59 ---
bug 41892 now logged for the concrete runtime problem I'm encountering.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
--- Comment #4 from caolanm at redhat dot com 2009-10-27 20:17 ---
At runtime of the original version of one of these loops (or a similar one, I
decided for ease to boil down to the warning case for this bug) goes way past
the RowSpan limits. If this one is cosmetic, then I've got anothe
--- Comment #3 from jakub at gcc dot gnu dot org 2009-10-27 16:53 ---
The issue is that for some strange reason VRP sees the loop iterator (which is
[0, 4) ) as VARYING. Then the fDum = get(b, b) is called when
b is not 3, and get uses the return maLine[nRow].get(nColumn); for nRow < 3.
--- Comment #2 from jakub at gcc dot gnu dot org 2009-10-27 16:33 ---
Reproduceable on today's trunk as well (s390x-linux target).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
--- Comment #1 from caolanm at redhat dot com 2009-10-27 14:47 ---
Created an attachment (id=18916)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=18916&action=view)
standalone demo
gcc -Wall -O2 -c demo.cxx
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41847
