--- Comment #5 from manu at gcc dot gnu dot org 2009-07-08 13:25 ---
(In reply to comment #3)
Note that getInt is completely inlined and there is no location involving
that function available anymore :/ The difficulties of C++ and late
diagnostics ...
Don't we keep
--- Comment #4 from manu at gcc dot gnu dot org 2009-04-29 13:16 ---
(In reply to comment #3)
Note that getInt is completely inlined and there is no location involving
that function available anymore :/ The difficulties of C++ and late
diagnostics ...
I wonder what Clang+LLVM
--- Comment #1 from edwintorok at gmail dot com 2009-04-25 09:39 ---
Created an attachment (id=17690)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17690action=view)
testcase
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39891
--- Comment #2 from rguenth at gcc dot gnu dot org 2009-04-25 10:41 ---
Thanks for the short testcase. I'll try to improve the location information.
The compiler at the point of the warning sees
D.1756_5 = (struct APSInt ) Val.Data;
AdditionalOffset.D.1723 = D.1756_5-D.1723;
and
--- Comment #3 from rguenth at gcc dot gnu dot org 2009-04-25 11:13 ---
The location is also correct in the sense that we try to warn with the
location
of the _dereference_. And that is indeed in APSInt APSInt::operator=(const
APSInt):
(void) (((struct APSInt *) this)-D.1723 =
