public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@redhat.com>
To: Jan Hubicka <jh@suse.cz>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: aliasing question
Date: Tue, 07 Sep 2004 14:22:00 -0000	[thread overview]
Message-ID: <1094566924.21733.36.camel@localhost.localdomain> (raw)
In-Reply-To: <20040907105142.GD28472@kam.mff.cuni.cz>

On Tue, 2004-09-07 at 06:51, Jan Hubicka wrote:

>   #   V_MUST_DEF <value_49>;
>   value = T.4862_48;
> 
> and alias1 dump:
> 
>   #   value_229 = V_MAY_DEF <value_19>;
>   value = T.4862_48;
> 
> Why the MUST_DEF is getting converted to MAY_DEF in such a obvious case
> for MUST_DEF?
> 
Before aliasing, 'value' did not belong to any alias set, but after
aliasing it is.  If we didn't do that, suppose that:

*p, alias tag TMT.1, alias set of TMT.1 = { value }

     1. p = (cond) ? &value : foo ();
     2. *p = 3;
     3. value = T.4862;
     4. return *p;

If you put a V_MUST_DEF in statement #3, you will consider '*p = 3'
dead.  Perhaps, we could put a V_MUST_DEF if there were more than one
element in TMT.1's alias set.  Not sure how much would that buy, but it
may be an interesting experiment.


Diego.

  reply	other threads:[~2004-09-07 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-07 10:51 Jan Hubicka
2004-09-07 14:22 ` Diego Novillo [this message]
2004-09-08 20:05   ` Jan Hubicka

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=1094566924.21733.36.camel@localhost.localdomain \
    --to=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jh@suse.cz \
    /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).