--- Comment #9 from pzhao at gcc dot gnu dot org 2010-06-02 06:53 ---
*** Bug 38468 has been marked as a duplicate of this bug. ***
--
pzhao at gcc dot gnu dot org changed:
What|Removed |Added
---
--- Comment #8 from manu at gcc dot gnu dot org 2010-02-22 22:32 ---
FIXED in GCC 4.5
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIG
--- Comment #7 from manu at gcc dot gnu dot org 2010-02-22 22:31 ---
Subject: Bug 43126
Author: manu
Date: Mon Feb 22 22:30:45 2010
New Revision: 156979
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=156979
Log:
2010-02-22 Manuel López-Ibáñez
PR c++/43126
--- Comment #6 from manu at gcc dot gnu dot org 2010-02-20 15:56 ---
I have a patch.
--
manu at gcc dot gnu dot org changed:
What|Removed |Added
AssignedTo|unassi
--- Comment #5 from manu at gcc dot gnu dot org 2010-02-20 15:31 ---
(In reply to comment #3)
> ("4:16"? I havn't seen that before. I hope gcc isn't going to start
> outputting character offsets by default; that's a lot of noise.)
>
>From GCC 4.5, you can disable it with -fno-show-co
--- Comment #4 from pinskia at gmail dot com 2010-02-20 09:00 ---
Subject: Re: "at this point in file" warnings are upside down
Sent from my iPhone
On Feb 19, 2010, at 10:51 PM, "glenn at zewt dot org" wrote:
>
>
> --- Comment #3 from glenn at zewt dot org 2010-02-20 06:51
Sent from my iPhone
On Feb 19, 2010, at 10:51 PM, "glenn at zewt dot org" > wrote:
--- Comment #3 from glenn at zewt dot org 2010-02-20 06:51
---
("4:16"? I havn't seen that before. I hope gcc isn't going to start
outputting character offsets by default; that's a lot of noise
--- Comment #3 from glenn at zewt dot org 2010-02-20 06:51 ---
("4:16"? I havn't seen that before. I hope gcc isn't going to start
outputting character offsets by default; that's a lot of noise.)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43126
--- Comment #2 from pinskia at gcc dot gnu dot org 2010-02-20 06:27 ---
I should say the simple example was:
int f(int);
int g(int a, int b)
{
return f(a, b);
}
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43126
--- Comment #1 from pinskia at gcc dot gnu dot org 2010-02-20 06:25 ---
Confirmed.
The C front-end just emits:
t.c: In function g:
t.c:4:3: error: too many arguments to function f
While the C++ front-end emits:
t.c:1:5: error: too many arguments to function int f(int)
t.c:4:16: er
10 matches
Mail list logo