[Bug c/56724] sub-optimal location in error

2018-01-25 Thread dmalcolm at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 David Malcolm changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug c/56724] sub-optimal location in error

2015-12-04 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Richard Biener changed: What|Removed |Added Target Milestone|5.3 |5.4 --- Comment #19 from Richard

[Bug c/56724] sub-optimal location in error

2015-12-04 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Manuel López-Ibáñez changed: What|Removed |Added CC|manu at gcc dot gnu.org| Target Milestone|5.4

[Bug c/56724] sub-optimal location in error

2015-07-16 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Richard Biener rguenth at gcc dot gnu.org changed: What|Removed |Added Target Milestone|5.2 |5.3 ---

[Bug c/56724] sub-optimal location in error

2015-04-22 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added Target Milestone|5.0 |5.2 --- Comment

[Bug c/56724] sub-optimal location in error

2014-09-11 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #15 from Manuel López-Ibáñez manu at gcc dot gnu.org --- Marek, is this fixed? Can we close it?

[Bug c/56724] sub-optimal location in error

2014-09-11 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #16 from Marek Polacek mpolacek at gcc dot gnu.org --- What's not fixed is this: r.c:3:5: note: expected ‘int (*)(double *)’ but argument is of type ‘int (*)(int *)’ int callf (int, int, int (*)(double *)); ^ we should point to

[Bug c/56724] sub-optimal location in error

2014-06-05 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #14 from Marek Polacek mpolacek at gcc dot gnu.org --- Author: mpolacek Date: Thu Jun 5 09:35:05 2014 New Revision: 211261 URL: http://gcc.gnu.org/viewcvs?rev=211261root=gccview=rev Log: PR c/56724 * c-typeck.c

[Bug c/56724] sub-optimal location in error

2014-06-04 Thread tromey at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #12 from Tom Tromey tromey at gcc dot gnu.org --- I noticed this patch today and tried it out on my current test case, which uses -Wc++-compat... unfortunately it still fails. Test code: extern void xfer (int, int, unsigned char *);

[Bug c/56724] sub-optimal location in error

2014-06-04 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #13 from Marek Polacek mpolacek at gcc dot gnu.org --- Yea, you're right, not everything has been fixed. I'll fix up this specific case in a bit, thanks for reporting it.

[Bug c/56724] sub-optimal location in error

2014-05-27 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #11 from Marek Polacek mpolacek at gcc dot gnu.org --- Author: mpolacek Date: Tue May 27 20:14:22 2014 New Revision: 210980 URL: http://gcc.gnu.org/viewcvs?rev=210980root=gccview=rev Log: PR c/56724 * c-typeck.c

[Bug c/56724] sub-optimal location in error

2014-05-25 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|NEW |ASSIGNED

[Bug c/56724] sub-optimal location in error

2014-05-19 Thread mpolacek at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #9 from Marek Polacek mpolacek at gcc dot gnu.org --- (In reply to Tom Tromey from comment #5) I tried this today with a recent-ish gcc trunk build, and there's been a regression. Now: barimba. gcc --syntax-only r.c r.c: In

[Bug c/56724] sub-optimal location in error

2014-05-16 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #8 from Manuel López-Ibáñez manu at gcc dot gnu.org --- (In reply to Tom Tromey from comment #5) I tried this today with a recent-ish gcc trunk build, and there's been a regression. I think the problem is that

[Bug c/56724] sub-optimal location in error

2014-05-15 Thread tromey at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #5 from Tom Tromey tromey at gcc dot gnu.org --- I tried this today with a recent-ish gcc trunk build, and there's been a regression. Now: barimba. gcc --syntax-only r.c r.c: In function ‘docall’: r.c:7:10: warning: passing argument

[Bug c/56724] sub-optimal location in error

2014-05-15 Thread manu at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Manuel López-Ibáñez manu at gcc dot gnu.org changed: What|Removed |Added CC||manu at gcc

[Bug c/56724] sub-optimal location in error

2014-05-15 Thread tromey at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #7 from Tom Tromey tromey at gcc dot gnu.org --- (In reply to Manuel López-Ibáñez from comment #6) (In reply to Tom Tromey from comment #5) The new situation is much worse for me as it prevents automated rewriting... What

[Bug c/56724] sub-optimal location in error

2014-03-26 Thread mpolacek at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 Marek Polacek mpolacek at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last

[Bug c/56724] sub-optimal location in error

2013-03-25 Thread tromey at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #1 from Tom Tromey tromey at gcc dot gnu.org 2013-03-25 18:44:37 UTC --- This affects g++ as well.

[Bug c/56724] sub-optimal location in error

2013-03-25 Thread pinskia at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #2 from Andrew Pinski pinskia at gcc dot gnu.org 2013-03-25 18:45:24 UTC --- (In reply to comment #0) t.c: In function ‘docall’: t.c:8:3: warning: passing argument 3 of ‘callf’ from incompatible pointer type [enabled by default]

[Bug c/56724] sub-optimal location in error

2013-03-25 Thread tromey at gcc dot gnu.org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56724 --- Comment #3 from Tom Tromey tromey at gcc dot gnu.org 2013-03-25 18:46:47 UTC --- (In reply to comment #2) Though it does say the 3rd argument though. Sure, it is just nicer if the compiler counts commas instead of me doing it.