public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jim Wilson <wilson@tuliptree.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/9997: Coelesce stack slots for disjoint scopes.
Date: Sun, 09 Mar 2003 15:56:00 -0000	[thread overview]
Message-ID: <20030309155600.10062.qmail@sources.redhat.com> (raw)

The following reply was made to PR middle-end/9997; it has been noted by GNATS.

From: Jim Wilson <wilson@tuliptree.org>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: middle-end/9997: Coelesce stack slots for disjoint scopes.
Date: Sun, 09 Mar 2003 10:52:33 -0500

 I believe we have tried this in the past, and ran into aliasing
 problems.  Suppose you have two variables of different types defined in
 different scopes.  Suppose the scheduler reorders instructions causing
 the scopes to overlap.  Now you do an alias test, and the alias code
 says that two references can't possibly alias because they have
 different types, but they do, because they were allocated to the same
 stack slot.  You can't rely on a test for the same address, because we
 may have lost address info in the RTL.
 
 We have different and better alias code now, so perhaps there is a way
 to address this.  Maybe if we add scope nesting level info to the alias
 info, and then assume that locals alias if they are in different scopes
 with a common parent, and neither is a parent of the other.
 
 Jim
 


             reply	other threads:[~2003-03-09 15:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-09 15:56 Jim Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-30  6:26 Jim Wilson
2003-04-30  6:16 Jim Wilson
2003-03-10  3:16 Jim Wilson
2003-03-09 20:46 Daniel Jacobowitz
2003-03-09 16:36 Jim Wilson
2003-03-08 20:26 Daniel Jacobowitz
2003-03-08 17:56 Daniel Jacobowitz
2003-03-08  6:11 bangerth
2003-03-08  1:06 rth

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=20030309155600.10062.qmail@sources.redhat.com \
    --to=wilson@tuliptree.org \
    --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).