This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug java/15133] gcjh generates wrong method signatures
- From: "rmathew at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 27 Apr 2004 10:25:28 -0000
- Subject: [Bug java/15133] gcjh generates wrong method signatures
- References: <20040425154237.15133.konqueror@gmx.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From rmathew at gcc dot gnu dot org 2004-04-27 10:25 -------
The problem is that disambiguation using arguments should only happen
for *native* overloaded methods - in this case, even a non-native
method triggers the disambiguation logic.
More specifically, in gjavah.c we should also keep track of
whether a method seen before was native and use this information in
overloaded_jni_method_exists_p().
I have a patch for this which I will submit shortly, assuming it
passes all tests - it certainly resolves this particular testcase
and also behaves correctly when more overloaded native methods
are present.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=15133