public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dan Nicolaescu <dann@godzilla.ICS.UCI.EDU>
To: java@gcc.gnu.org
Subject: java aliasing rules
Date: Wed, 27 Mar 2002 11:43:00 -0000	[thread overview]
Message-ID: <200203271143.aa05958@gremlin-relay.ics.uci.edu> (raw)

Given this code:

class first  {  int i; char a;  char f1;  char f2; double d;};
class second {  char b;  char f2;  int f3;};


public class t
{
    public  void f (first  ps1, second ps2)
    {
        ps1.f1++;
        ps2.f2++;
        ps1.f1++;
        ps2.f2++;
    }
}

can it be assumed that given that "first" and "second" are
incompatible then ps1.f1 and ps2.f2 don't alias and we can generate
code like the following: (SPARC assembly)

        !#PROLOGUE# 0
        !#PROLOGUE# 1
        lduh    [%o1+14], %o0
        lduh    [%o2+10], %o3
        add     %o0, 2, %o0
        add     %o3, 2, %o3
        sth     %o0, [%o1+14]
        retl
        sth     %o3, [%o2+10]

instead of what is generated now: 

        !#PROLOGUE# 0
        !#PROLOGUE# 1
        lduh    [%o1+14], %o3
        add     %o3, 1, %o3
        sth     %o3, [%o1+14]
        lduh    [%o2+10], %o0
        add     %o0, 1, %o0
        sth     %o0, [%o2+10]
        lduh    [%o1+14], %o3
        add     %o3, 1, %o3
        sth     %o3, [%o1+14]
        lduh    [%o2+10], %o0
        add     %o0, 1, %o0
        retl
        sth     %o0, [%o2+10]


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.  If the above is not true, is there a
restricted case when it is true?


(for the curious this is related to the patch at
http://gcc.gnu.org/ml/gcc-patches/2002-03/msg00576.html that is not
totally correct for C, but I have a hunch that it might be OK for
java, if that is the case I will change the patch to be language
specific).

             reply	other threads:[~2002-03-27 19:43 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-27 11:43 Dan Nicolaescu [this message]
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
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=200203271143.aa05958@gremlin-relay.ics.uci.edu \
    --to=dann@godzilla.ics.uci.edu \
    --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).