public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/26390] Problem dispatching method call when method does not exist in superclass
Date: Mon, 13 Mar 2006 17:12:00 -0000	[thread overview]
Message-ID: <20060313171251.9074.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26390-11339@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from tromey at gcc dot gnu dot org  2006-03-13 17:12 -------
I added a main to the reduced test case:

  public static void main(String[] args)
  {
    SwingFramePeer s = new SwingFramePeer();
    s.setBounds();
  }

With this I can almost reproduce the original bug:

opsy. gcj --main=pr26390 -o P pr26390.java
/tmp/cczetk2m.o(.text+0xd): In function `void
pr26390$SwingFramePeer::setBounds()':
pr26390.java: undefined reference to `void pr26390$WindowPeer::setBounds()'

I say "almost" since from the original report I would expect
the missing method to come from SwingWindowPeer.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26390


  parent reply	other threads:[~2006-03-13 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21  8:32 [Bug java/26390] New: " david at jpackage dot org
2006-02-22 14:31 ` [Bug java/26390] " pinskia at gcc dot gnu dot org
2006-03-09  3:16 ` mckinlay at redhat dot com
2006-03-10 18:13 ` mark at gcc dot gnu dot org
2006-03-10 23:00 ` tromey at gcc dot gnu dot org
2006-03-11  1:40 ` tromey at gcc dot gnu dot org
2006-03-13 17:10 ` tromey at gcc dot gnu dot org
2006-03-13 17:12 ` tromey at gcc dot gnu dot org [this message]
2006-03-13 19:07 ` tromey at gcc dot gnu dot org
2006-03-15 18:29 ` tromey at gcc dot gnu dot org
2006-03-15 18:31 ` tromey at gcc dot gnu dot org
2006-03-29 16:32 ` tromey at gcc dot gnu dot org
2006-03-29 16:36 ` tromey at gcc dot gnu dot org
2006-12-28 15:45 ` rob1weld at aol 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=20060313171251.9074.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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: link
Be 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).