[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2024-01-23 Thread mpolacek at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 Bug 7 depends on bug 43486, which changed state. Bug 43486 Summary: Preserve variable-use locations https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43486 What|Removed |Added

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2018-05-30 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2018-05-30 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 --- Comment #9 from Jonathan Wakely --- Author: redi Date: Wed May 30 23:13:48 2018 New Revision: 260979 URL: https://gcc.gnu.org/viewcvs?rev=260979&root=gcc&view=rev Log: PR c++/7 improve location for diagnostic Pass in the location of the

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2018-03-23 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 Jonathan Wakely changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|dmalcolm a

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2018-03-16 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 David Malcolm changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org Ta

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2018-03-16 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2017-08-22 00:00:00 |2018-3-16 --- Comment #6 from Jonathan

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2017-08-22 Thread egallager at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 Eric Gallager changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 --- Comment #4 from David Malcolm --- FWIW the location information is available in the frame above: Breakpoint 6, invalid_nonstatic_memfn_p (loc=205792, expr=, complain=3) at ../../src/gcc/cp/typeck.c:1834 1834ex

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 --- Comment #3 from Jonathan Wakely --- Or maybe even better, make the caret point to the member function, but cover the entire expression: x.foo ~~^~~ (Please ignore the "did you mean...?" part shown in the initial comment, that w

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread redi at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 --- Comment #2 from Jonathan Wakely --- (In reply to David Malcolm from comment #1) > (In reply to Jonathan Wakely from comment #0) > > There are lots of cases where we should use rich locations, but here's one > Do you mean a fix-it hint? I don

[Bug c++/77777] Use rich location to mark correct expression for "invalid use of non-static member function"

2016-09-28 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=7 David Malcolm changed: What|Removed |Added CC||dmalcolm at gcc dot gnu.org --- Comment