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: Wed, 30 Apr 2003 06:26:00 -0000	[thread overview]
Message-ID: <20030430062601.432.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: Daniel Jacobowitz <drow@mvista.com>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: middle-end/9997: Coelesce stack slots for disjoint scopes.
Date: 29 Apr 2003 23:19:28 -0400

 While looking at this, I noticed that the var_temp_slot_level stuff
 seems to be broken.  In expand_expr, case SAVE_EXPR, we call assign_temp
 with keep == 3.  This ends up using var_temp_slot_level.  However, there
 is no place in the compiler that ever sets var_temp_slot_level.  It is
 initialized to 0, so all SAVE_TEMP temps end up at level 0, which means
 they live until the end of the function.  This can't be right.  I
 suspect this was also broken by the functions-as-trees stuff.  I haven't
 looked into this yet.  We can perhaps open a new PR for this problem.
 
 Jim
 
 


             reply	other threads:[~2003-04-30  6:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-30  6:26 Jim Wilson [this message]
  -- strict thread matches above, loose matches on Subject: below --
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-09 15:56 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=20030430062601.432.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).