This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/20164] [3.4/4.0/4.1 Regression] Wrong line number in diagnostic
- From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 21 Oct 2005 16:10:10 -0000
- Subject: [Bug c++/20164] [3.4/4.0/4.1 Regression] Wrong line number in diagnostic
- References: <bug-20164-7559@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #10 from mmitchel at gcc dot gnu dot org 2005-10-21 16:10 -------
Andrew, why do you say that the location of the diagnostics in comment #5?
I get:
/home/mitchell/tmp/pr20164.cpp: In function 'void Bar2()':
/home/mitchell/tmp/pr20164.cpp:19: error: no matching function for call to
'Par\
m::Parm(temp&)'
/home/mitchell/tmp/pr20164.cpp:7: note: candidates are: Parm::Parm()
/home/mitchell/tmp/pr20164.cpp:7: note: Parm::Parm(const Parm&)
That's reasonable; line 19 is the call, and line 7 is the opening curly brace
for "Parm", which is a good location for the implicitly declared constructors.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20164