public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: java/5042: java: wrong addressing of inner class attributes
Date: Wed, 29 May 2002 23:56:00 -0000	[thread overview]
Message-ID: <20020530062602.30983.qmail@sources.redhat.com> (raw)

The following reply was made to PR java/5042; it has been noted by GNATS.

From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: java/5042: java: wrong addressing of inner class attributes
Date: Thu, 30 May 2002 18:19:09 +1200

 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5042
 
 I've just been looking at the code produced by the current GCJ for 
 AbstractCharReader.scanExpectedName:
 
     movl    16(%ebp), %eax    #  expectedName,  expectedName
     movzwl    12(%ebp), %edx    #  fastcheck
     movl    8(%ebp), %ebx    #  this,  this
     cmpb    $11, 
 _ZN3org6apache6xerces5utils22XMLCharacterProperties6class$E+74    #  
 <variable>.state
     movl    52(%ebx), %esi    #  <variable>.fMostRecentChar,  ch
     movl    %edx, -16(%ebp)    #  fastcheck
     movl    8(%eax), %edx    #  <variable>.chars
 
 
 Here the expectedName.chars field is accessed at offset 8 which seems 
 correct to me (the first two fields are the class pointer and this$0).
 
 Does this bug still occur with GCc 3.1 or newwer or should I close this PR?
 
 regards
 
 Bryce.
 
 


             reply	other threads:[~2002-05-30  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-29 23:56 Bryce McKinlay [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-23 21:11 neroden
2002-10-08  7:07 aph
2001-12-07  6:36 roland

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=20020530062602.30983.qmail@sources.redhat.com \
    --to=bryce@waitaki.otago.ac.nz \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).