public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug java/22060] javax/swing/text/InternationalFormatter.clone() doesn't compile (GNU Classpath) Date: Wed, 15 Jun 2005 19:42:00 -0000 [thread overview] Message-ID: <20050615194249.28945.qmail@sourceware.org> (raw) In-Reply-To: <20050614104518.22060.mark@gcc.gnu.org> ------- Additional Comments From tromey at gcc dot gnu dot org 2005-06-15 19:42 ------- I looked at this a little bit. There are two choices for the problem here. One is that find_applicable_accessible_methods_list is returning too much. For the call in question, it returns Object.clone, Inner.clone, and Bar.clone However, this seems to be what is intended. The second choice for the problem is that find_most_specific_methods_list is not correctly removing Inner.clone from the list of most specific methods. This function is a bit strange in that it has special cases for inner classes, e.g.: int v = (DECL_SPECIFIC_COUNT (current_v) += (INNER_CLASS_TYPE_P (DECL_CONTEXT (current_v)) ? 2 : 1)); ... which don't make sense to me. -- What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |4.0.0 4.1.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22060
next prev parent reply other threads:[~2005-06-15 19:42 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-06-14 10:45 [Bug java/22060] New: " mark at gcc dot gnu dot org 2005-06-14 10:48 ` [Bug java/22060] " roman at kennke dot org 2005-06-14 11:43 ` rmathew at gcc dot gnu dot org 2005-06-14 11:44 ` rmathew at gcc dot gnu dot org 2005-06-15 19:42 ` tromey at gcc dot gnu dot org [this message] 2005-06-15 20:13 ` tromey at gcc dot gnu dot org 2005-06-15 22:07 ` mckinlay at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20050615194249.28945.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).