public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryce McKinlay <bryce@waitaki.otago.ac.nz>
To: Dan Nicolaescu <dann@godzilla.ics.uci.edu>
Cc: java@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: java aliasing rules
Date: Wed, 27 Mar 2002 15:54:00 -0000	[thread overview]
Message-ID: <3CA25B77.1000108@waitaki.otago.ac.nz> (raw)
In-Reply-To: <200203271143.aa05958@gremlin-relay.ics.uci.edu>

Dan Nicolaescu wrote:

>The more general question is if 2 COMPONENT_REFs that refer to classes
>that are in conflicting alias sets (ie alias_sets_conflict_p) alias in
>java. I have a hunch that this might be true, but I don't know enough
>about java to be sure.
>

Right - Aliasing in Java is very simple, because basically there isn't 
any ;-). The only case we need to be careful about is with inheritance 
when two fields in different classes might actually be the same (ie if 
"class second extends first").

I implemented java_get_alias_set() by simply assigning a new alias set 
to every unique field, storing it in DECL_POINTER_ALIAS_SET for each 
FIELD_DECL. This managed to eliminate some redundant loads in my tests, 
but didn't cause any measurable improvements in benchmark scores so I 
didn't get too excited about it, and I didn't get around to submitting 
the patch yet. I'll try it out later on your test case and see what 
happens...

regards

Bryce.


  parent reply	other threads:[~2002-03-27 23:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 11:43 Dan Nicolaescu
2002-03-27 13:53 ` Tom Tromey
2002-03-27 16:03   ` Dan Nicolaescu
2002-03-27 16:47     ` Tom Tromey
2002-03-27 20:00       ` Dan Nicolaescu
2002-03-27 15:54 ` Bryce McKinlay [this message]
2002-03-27 16:45   ` Tom Tromey
2002-03-28 22:02     ` Bryce McKinlay
2002-03-28 22:13       ` Richard Henderson
2002-03-28 22:15       ` Tom Tromey
2002-03-29 15:22         ` Bryce McKinlay
2002-03-29 16:26           ` Richard Henderson
2002-03-30  6:37           ` Jeff Sturm
2002-03-30 13:55             ` Richard Henderson
2002-03-30 15:04             ` Bryce McKinlay
2002-04-04 10:57               ` Jeff Sturm
2002-04-04 12:57                 ` Andrew Haley
2002-04-04 14:20                   ` Jeff Sturm
2002-04-04 17:04                 ` Bryce McKinlay
2002-04-04 20:39                   ` Jeff Sturm
2002-04-05  1:07                     ` Bryce McKinlay

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=3CA25B77.1000108@waitaki.otago.ac.nz \
    --to=bryce@waitaki.otago.ac.nz \
    --cc=dann@godzilla.ics.uci.edu \
    --cc=gcc@gcc.gnu.org \
    --cc=java@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).