http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54895
Kai Tietz <ktietz at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-11-22
Ever Confirmed|0 |1
--- Comment #6 from Kai Tietz <ktietz at gcc dot gnu.org> 2012-11-22 18:48:18
UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> > This is most likely a duplicate of already fixed PR/55268.
>
> I checked upon the 193725 revision.
> The first test gives the same result. The second test now gives the wrong
> result(1). Before this the result of the second test was right.
Well, the first test fails due the calling-convention isn't part of the
signature in C++. For C you will get for this code simply a double-definition.
Issue here is that we don't get an error for g++ as it detects that a types
are different for both myfoo functions.
The second case checks something different. That it now returns 1 is correct
due types are different due different calling-convention used.
So remaining testcase is the first one.
